io.github.presidio-v/presidio-hardened-x402-mcp
PYPI · PRESIDIO-HARDENED-X402-MCP · SCANNED SEP 22
Pre-payment PII screener for x402 — catches emails, SSNs, names before agents sign.
Available components
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 Security41
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects cryptography 48.0.1, reached via presidio-hardened-x402 > presidio-anonymizer > cryptography. A fixed version is available. View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 8 of 83 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 50 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 756 tokens (~252/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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
{
"mcpServers": {
"presidio-v-presidio-hardened-x402-mcp": {
"command": "uvx",
"args": [
"presidio-hardened-x402-mcp"
]
}
}
} {
"servers": {
"presidio-v-presidio-hardened-x402-mcp": {
"command": "uvx",
"args": [
"presidio-hardened-x402-mcp"
]
}
}
} codex mcp add presidio-v-presidio-hardened-x402-mcp -- uvx presidio-hardened-x402-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"presidio-v-presidio-hardened-x402-mcp": {
"type": "local",
"command": [
"uvx",
"presidio-hardened-x402-mcp"
],
"enabled": true
}
}
} openclaw mcp add presidio-v-presidio-hardened-x402-mcp --command uvx --arg presidio-hardened-x402-mcp
mcp_servers:
presidio-v-presidio-hardened-x402-mcp:
command: "uvx"
args: ["presidio-hardened-x402-mcp"] {
"McpServers": {
"presidio-v-presidio-hardened-x402-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"presidio-hardened-x402-mcp"
]
}
}
} assistant mcp add presidio-v-presidio-hardened-x402-mcp -t stdio -c uvx -a presidio-hardened-x402-mcp
{
"mcpServers": {
"presidio-v-presidio-hardened-x402-mcp": {
"command": "uvx",
"args": [
"presidio-hardened-x402-mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 −2
- Stability: pass → 0.80 functional
- 11 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass 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 22 Sept 2026 · Analysed pypi/presidio-hardened-x402-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g6cj-pr64-35w5 | CVE-2026-69247 | high | yes | |
| GHSA-jwv3-5hgf-82ww | CVE-2026-69249 | high | yes | |
| GHSA-m2h6-j472-rp4c | CVE-2026-69248 | medium | yes | |
| PYSEC-2026-3552 | CVE-2026-69247 | none | yes | |
| PYSEC-2026-3553 | CVE-2026-69249 | none | yes | |
| PYSEC-2026-3554 | CVE-2026-69248 | none | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 83 packages
| Packages resolved | 83 |
|---|---|
| Deprecated | 1 |
| Stale | 7 |
| 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 ~172
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 (used for per-endpoint limits). amount_usd: Payment amount in USD-equivalent. Returns: {"allowed": true} on success, or {"allowed": false, "reason": str, "limit_usd": float, "amount_usd": float}.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | – |
| resource_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_payment_replay ~219
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. Returns: {"is_replay": false, "fingerprint": "<hex>"} on first seen, or {"is_replay": true, "fingerprint": "<hex>"} on duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| currency | string | yes | – |
| deadline_seconds | integer | yes | – |
| pay_to | string | yes | – |
| resource_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
screen_payment_metadata ~365
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"). 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.
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 PII screener for x402, catches emails, SSNs, names before agents sign. 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 59 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 22 September 2026. 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 756 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.