PIO Public Information and Cost Estimates MCP server
io.github.PayInOne/pio-publicPayInOnestreamable-httpv1.0.0Scanned
Public PIO product information and hypothetical employment-cost estimates. No account required.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the PIO Public Information and Cost Estimates MCP server can do
The PIO Public Information and Cost Estimates MCP server is published by the GitHub account PayInOne. It has 3 tools. It can create or change data (1 tool: estimate_employer_cost), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (estimate_employer_cost and get_employer_cost_estimate).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
estimate_employer_costSubmit an anonymous hypothetical salary scenario to the PIO website calculator.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Submit an anonymous hypothetical salary scenario to the PIO website calculator. This creates a calculation job, never an employee, bill or payment. Do not use employee records or personal/company information. Explicit country, currency, period and gross/net basis are required. A processing response contains no confirmed amount: poll get_employer_cost_estimate with the returned estimate_id after retryAfterSeconds. Identical scenarios from the same caller resume the same job for 29 minutes. Totals cover returned components only; fees, deposits and unlisted benefits are not confirmed.
Annotations the server declares
- title: Estimate hypothetical employment cost
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
get_employer_cost_estimateRead the calculation created by estimate_employer_cost using its opaque estimate_id.Reads text others writeNo findings
Why it is in this group
- The name "get_employer_cost_estimate" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Read the calculation created by estimate_employer_cost using its opaque estimate_id. Keep that handle private. A completed calculation remains an estimate, not a quote or a complete employer cost. Do not resubmit a processing scenario.
Annotations the server declares
- title: Read employment cost estimate
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_public_product_factsRead reviewed public PIO product information with source URLs.No findings
Why it is in this group
- The name "get_public_product_facts" says "get": a word for reading.
Description, as the server wrote it Read reviewed public PIO product information with source URLs. Select a topic; no account, team, employee information or private knowledge is accessed. This does not quote customer-specific pricing.
Annotations the server declares
- title: PIO public product information
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:22 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.pioinc.com/gateway/foundation/mcpPublic: tools/list returned 3 tools to an anonymous client, including estimate_employer_cost (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pio-public https://app.pioinc.com/gateway/foundation/mcpPublicclaude mcp add --transport http pio-public https://app.pioinc.com/gateway/foundation/mcpPublicRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pio-public__get_public_product_facts",
"mcp__pio-public__get_employer_cost_estimate"
],
"ask": [
"mcp__pio-public__estimate_employer_cost"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pio-public. Review it before you use it.
Capability tags behind 2 rules
- mcp__pio-public__estimate_employer_cost untrusted-input
- mcp__pio-public__get_employer_cost_estimate untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.PayInOne/pio-public/verify?hash=ecad47087b9a4601990db86dc077ba1fac964c80357fd21790b3b88a38ae05b6" | jq -e '.changed == false'Pinned hash ecad47087b9a, from Nov 20, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.PayInOne/pio-public/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.PayInOne/pio-public)Source: MCP Registry. Synced Nov 6, 2026, 16:17 UTC.
PIO Public Information and Cost Estimates MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PIO Public Information and Cost Estimates MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the PIO Public Information and Cost Estimates MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the PIO Public Information and Cost Estimates MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the PIO Public Information and Cost Estimates MCP server have?
- 3 tools: 1 write, 2 read. estimate_employer_cost, get_public_product_facts and get_employer_cost_estimate.
Does the PIO Public Information and Cost Estimates MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PIO Public Information and Cost Estimates MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the PIO Public Information and Cost Estimates MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.