Skip to main content
Glama
presidio-v

presidio-hardened-x402-mcp

by presidio-v
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to presidio-hardened-x402-mcp

No user-submitted related servers found.

    Related Servers

    • 402sentinel-mcp

      kaditang
      A
      license
      A
      quality
      C
      maintenance
      MCP 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.
      10
      44 npm
      1
      MIT

    • pulsefeed-x402-mcp

      Nikolife2016
      A
      license
      A
      quality
      B
      maintenance
      Before 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.
      3
      MIT
    • TWZRD Agent Intel by twzrd-sol

      TWZRD Agent Intelofficial

      twzrd-sol
      A
      license
      Not graded
      quality
      A
      maintenance
      Pre-spend trust layer for agents paying over x402 on Solana, providing seller vetting and readiness checks before USDC leaves the wallet.
      MIT

    • ada-wallet

      loveaihq
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to pay x402 endpoints on Cardano through a policy-gated wallet with spend caps, payee allowlists, human approval, and an audit log.
      1,341 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a completely distinct purpose: PII screening, spending policy enforcement, and replay protection. The descriptions clearly delineate their roles, leaving no ambiguity about which tool to use for each pre-payment check.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun pattern in snake_case (screen_payment_metadata, check_payment_policy, check_payment_replay). The verbs 'screen' and 'check' accurately differentiate the actions, and the nouns clearly indicate the target aspect of payment processing.

    Tool Count5/5

    Three tools cover the essential pre-payment validation steps (privacy, policy, replay) without unnecessary overlap or bloat. This is a well-scoped set that fully serves the server's stated purpose.

    Completeness5/5

    The tool surface provides a complete set of checks needed before submitting an x402 payment: PII redaction, spending limit verification, and replay detection. There are no obvious gaps for the declared pre-payment domain.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources