io.github.presidio-v/presidio-hardened-x402-mcp
PYPI · PRESIDIO-HARDENED-X402-MCP
Pre-payment safety gate for x402 agents: PII screening, spend policy, replay checks before signing.
Available components
Last scanned (12 hours ago)
Scores higher than 69% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 8 of 84 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to presidio-v/presidio-hardened-x402-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 916 tokens (~305/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 3 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
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.1 → 0.4.0 functional
- 20 Nov 26 +17
- Malware scan: unverified → pass ▲ security
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.97 functional
- 19 Nov 26 −17
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → partial ▼ security
- Dependency health: 0.97 → partial functional
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.1.1 → 0.4.0 functional
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Nov 26 +1
- Stability: 0.97 → pass security
- 15 Nov 26 +14
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 14 Nov 26 −15
- Malware scan: pass → unverified ▼ security
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 · Analysed pypi/presidio-hardened-x402-mcp@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | presidio-v/presidio-hardened-x402-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/presidio-v/presidio-hardened-x402-mcp/.github/workflows/release.yml@refs/tags/v0.4.0 |
| Rekor log index | 3745223699 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ff9983b258d732827e5a28352cb89e34c947c0af53483ab45ab9fd88678d4ea5 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 84 packages
| Packages resolved | 84 |
|---|---|
| Stale | 7 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_payment_policy ~259
Check whether a payment is allowed by the configured spending policy. WARNING: this records the spend against rolling time-window ledgers. Call exactly once, immediately before submitting the payment. If you call this and then do not pay, the spend window will be inflated until it rolls over. Configure limits at server startup via PRESIDIO_X402_MCP_* env vars. Args: resource_url: x402 resource URL being paid. Screened first; only the redacted URL reaches the policy engine (per-endpoint limits match on it, so keep PII out of configured endpoint prefixes). amount_usd: Payment amount in USD-equivalent. prior_decision_refs: Optional decision_ref values this server returned earlier for the same payment (e.g. from screen_payment_metadata); linked into the signed record. Max 8. Returns: {"allowed": true} on success, or {"allowed": false, "reason": str, "limit_usd": float, "amount_usd": float}; plus decision_ref when signed decision evidence is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | – |
| prior_decision_refs | – | – | – |
| resource_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_payment_replay ~269
Check whether this exact payment has been seen recently (replay protection). WARNING: this records the fingerprint. Call exactly once, immediately before submitting the payment. Cross-process detection requires PRESIDIO_X402_FINGERPRINT_KEY (and optionally PRESIDIO_X402_MCP_REDIS_URL); otherwise each MCP server process has its own ephemeral in-memory store. Args: resource_url: x402 resource URL. pay_to: Recipient address. amount: Amount as string (preserves precision). currency: Currency symbol (e.g. "USDC"). deadline_seconds: Payment deadline as epoch seconds. prior_decision_refs: Optional decision_ref values this server returned earlier for the same payment; linked into the signed record. Max 8. Returns: {"is_replay": false, "fingerprint": "<hex>"} on first seen, or {"is_replay": true, "fingerprint": "<hex>"} on duplicate; plus decision_ref when signed decision evidence is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| currency | string | yes | – |
| deadline_seconds | integer | yes | – |
| pay_to | string | yes | – |
| prior_decision_refs | – | – | – |
| resource_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_payment_metadata ~388
Screen x402 payment metadata for PII before signing the payment. Call BEFORE sending the payment request. Detects emails, phone numbers, SSNs, names, and other PII in the resource URL, description, and reason fields and returns redacted strings plus per-field entity counts. No side effects. Runs in one of two modes: - in_process (default): wraps the local presidio_x402 PIIFilter. - remote: when both PRESIDIO_X402_MCP_REMOTE_BASE_URL and ..._REMOTE_API_KEY are set, POSTs to /v1/screen on that host for centralized audit. On remote failure, returns a structured error dict instead of silently falling back — the caller must decide whether to retry, accept reduced screening, or abort. Args: resource_url: x402 resource URL the agent is about to pay (max 2048 chars). description: Human-readable description (max 4096 chars). reason: Reason / memo string (max 4096 chars). entities: Optional whitelist of Presidio entity types to detect. If None, all configured entities are scanned. Returns: On success: dict with keys redacted_resource_url, redacted_description, redacted_reason, entities_found (list of {entity_type, field, count}), and mode (one of "in_process", "remote"); plus decision_ref when signed decision evidence is enabled (pass it to the gates as prior_decision_refs). On remote failure: dict with keys error (one of "auth_error", "rate_limit", "unavailable"), detail, optional retry_after (for rate_limit), and mode ("remote").
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| entities | – | – | – |
| reason | string | – | – |
| resource_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.presidio-v/presidio-hardened-x402-mcp server?
io.github.presidio-v/presidio-hardened-x402-mcp runs locally as a PyPI package, launched with uvx presidio-hardened-x402-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · presidio-hardened-x402-mcp
claude mcp add presidio-v-presidio-hardened-x402-mcp -- uvx presidio-hardened-x402-mcp
What is the io.github.presidio-v/presidio-hardened-x402-mcp server?
io.github.presidio-v/presidio-hardened-x402-mcp is listed in the public MCP registry as io.github.presidio-v/presidio-hardened-x402-mcp. Pre-payment safety gate for x402 agents: PII screening, spend policy, replay checks before signing. This page covers its PyPI package (presidio-hardened-x402-mcp).
Is the io.github.presidio-v/presidio-hardened-x402-mcp server safe to use?
io.github.presidio-v/presidio-hardened-x402-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 io.github.presidio-v/presidio-hardened-x402-mcp server expose?
io.github.presidio-v/presidio-hardened-x402-mcp exposes 3 tools: screen_payment_metadata, check_payment_policy, check_payment_replay. Their descriptions and schemas cost roughly 916 tokens of context every time the server is loaded.
Is the io.github.presidio-v/presidio-hardened-x402-mcp server still maintained?
io.github.presidio-v/presidio-hardened-x402-mcp 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 licence is the io.github.presidio-v/presidio-hardened-x402-mcp server under?
io.github.presidio-v/presidio-hardened-x402-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.presidio-v/presidio-hardened-x402-mcp server?
VerifyMCP ran 15 checks on io.github.presidio-v/presidio-hardened-x402-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.presidio-v/presidio-hardened-x402-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.