presidio-hardened-x402-mcp (presidio-v/presidio-hardened-x402-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100

presidio-hardened-x402-mcp

Pre-payment PII screener for x402 — MCP server wrapping presidio-hardened-x402

→ presidio-v/presidio-hardened-x402-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

presidio-v

Source: Glama · also listed on github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored hereGitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: PRESIDIO_X402_MCP_REMOTE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configPRESIDIO_X402_MCP_LOG_LEVELDEBUG / INFO / WARNING / ERROR INFO
configPRESIDIO_X402_MCP_PER_ENDPOINT_JSONPer-endpoint cap, e.g. '{"api.foo.com": 5.00}' unset
configPRESIDIO_X402_MCP_WINDOW_SECONDSRolling window for the daily limit 86400
configPRESIDIO_X402_MCP_AGENT_IDLabel written into audit records unset
configPRESIDIO_X402_MCP_AUDIT_PATHAppend-only JSON-L audit log path; omit to disable unset
configPRESIDIO_X402_MCP_MODEregex (zero-setup) or nlp (needs [nlp] extra + a spaCy model) regex
configPRESIDIO_X402_MCP_REPLAY_TTLFingerprint cache TTL (seconds) 300
configPRESIDIO_X402_MCP_REDIS_URLUse Redis for replay state instead of in-memory unset
configPRESIDIO_X402_MCP_REMOTE_BASE_URLEnable HTTP-proxy mode for tool 1 — see Modes unset
🔐 secretPRESIDIO_X402_MCP_REMOTE_API_KEYAPI key for the remote screening service unset
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/3 tools missing one or more hints — screen_payment_metadata (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_payment_policy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_payment_replay (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool handlers catch errors

2/3 tool handlers wrap calls in try/catch (67%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/presidio-v/presidio-hardened-x402-mcp)](https://m8ven.ai/mcp/presidio-v/presidio-hardened-x402-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 639397aa27861e535997a38f6a09a8abb307a224
code hash: 7787fd844973a4ad8741ba092d69434f83e839b6030084be38fc184f4e486569
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client