presidio-hardened-x402-mcp
Related Servers
Alternatives to presidio-hardened-x402-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for assessing counterparty risk in x402 payments using on-chain data, providing risk scores, decisions, and wallet spending policies to prevent fraud and unauthorized payments.101MIT
- AlicenseAqualityBmaintenanceBefore an AI agent pays an x402 endpoint, checks whether it's safe to pay: liveness, scam/anomaly scan (payTo hijack, bait-and-switch, honeypot), and on-chain receiver verification. ~70% of x402 endpoints are dead or scams.3MIT
- AlicenseAqualityBmaintenanceThis tool library gives AI agents a discovery and "know before you pay" layer to find useful services and check the historic reputation across >200,000 endpoints in the public x402 ecosystem.15237 npm1MIT
- AlicenseAqualityBmaintenanceSpend limits for AI agents that pay with x402: every paywall is policy-checked before a cent moves.5MIT
- AlicenseAqualityAmaintenanceEnables agents and developers to check x402 endpoints, assess scores and wallet risks, authorize payments with spending rules, and report outcomes before an agent pays.62MIT

TWZRD Agent Intelofficial
AlicenseNot gradedqualityBmaintenancePre-spend trust layer for agents paying over x402 on Solana, providing seller vetting and readiness checks before USDC leaves the wallet.MIT
TDQS
Scored across 3 tools
Each tool targets a distinct pre-payment concern: PII screening, spending-policy authorization, and replay detection. Their inputs overlap, but the roles are complementary and clearly separated by purpose and description.
All names use snake_case and follow a predictable verb_payment_<object> pattern. The slight verb variation (screen vs. check) reflects genuinely different actions while remaining consistent.
Three tools fit a focused pre-payment hardening pipeline, with each tool earning its place. There is no filler or redundant surface for this narrow scope.
The set covers the core safety checks: PII screening, policy limits, and replay protection. Minor gaps exist around inspecting configured policy limits or releasing recorded spend/fingerprints when a payment is not completed, though the warnings document these operational constraints.