Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PIO Public Information and Cost Estimates

REMOTE · APP.PIOINC.COM

Public PIO product information and hypothetical employment-cost estimates. No account required.

Available components

+4 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security77
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 413 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 9% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://app.pioinc.com/gateway/foundation/mcpPublic

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pioinc.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 acce04b4e50734e013288b58c2c4363b
SANs: pioinc.com, *.pioinc.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of app.pioinc.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
pioinc.com. DS published 2371 13 Verified
app.pioinc.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.pioinc.com/gateway/foundation/mcpPublic Verified 200
http (plaintext) http://app.pioinc.com/gateway/foundation/mcpPublic HTTPS enforced 301 https://app.pioinc.com/gateway/foundation/mcpPublic
MCP tools · 3 exposed · ~317 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
estimate_employer_cost ~192

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.

NameTypeReqDescription
country_codestringyes–
currencystringyes–
languagestring––
region_codestring|null––
salarynumberyes–
salary_basisstringyes–
salary_periodstringyes–
tax_yearinteger|null–Current year only, or null for the current year.
NameTypeReqDescription
availablebooleanyes–
messagestringyes–
statusstringyes–

No examples provided.

get_employer_cost_estimate ~64

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.

NameTypeReqDescription
estimate_idstringyes–
NameTypeReqDescription
availablebooleanyes–
messagestringyes–
statusstringyes–

No examples provided.

get_public_product_facts ~61

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.

NameTypeReqDescription
languagestring––
topicstringyes–
NameTypeReqDescription
availablebooleanyes–
messagestringyes–
statusstringyes–

No examples provided.

Install

How do I install the PIO Public Information and Cost Estimates MCP server?

PIO Public Information and Cost Estimates is a hosted endpoint at https://app.pioinc.com/gateway/foundation/mcpPublic, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.pioinc.com

# add to Claude Code
claude mcp add --transport http payinone-pio-public 'https://app.pioinc.com/gateway/foundation/mcpPublic'
Common questions

What is the PIO Public Information and Cost Estimates MCP server?

PIO Public Information and Cost Estimates is an MCP server listed in the public MCP registry as io.github.PayInOne/pio-public. Public PIO product information and hypothetical employment-cost estimates. No account required. This page covers its hosted endpoint (https://app.pioinc.com/gateway/foundation/mcpPublic).

Is the PIO Public Information and Cost Estimates MCP server safe to use?

PIO Public Information and Cost Estimates scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PIO Public Information and Cost Estimates MCP server expose?

PIO Public Information and Cost Estimates exposes 3 tools: get_public_product_facts, estimate_employer_cost, get_employer_cost_estimate. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.

Does the PIO Public Information and Cost Estimates MCP server require authentication?

No. We connected to PIO Public Information and Cost Estimates without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PIO Public Information and Cost Estimates MCP server still maintained?

PIO Public Information and Cost Estimates is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the PIO Public Information and Cost Estimates MCP server?

VerifyMCP ran 13 checks on PIO Public Information and Cost Estimates, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.