Skip to main content
Glama
Sign In
x402-firewall

x402-firewall

by x402-firewall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to x402-firewall

No user-submitted related servers found.

    Related Servers

    • agent-x402

      rustemmustafingovua-byte
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to check their wallet address and USDC balance, preview the cost of an x402 call, and pay for API requests in USDC on Base without an account or API key. Spend caps, allow-lists and blocked contracts are enforced in code before anything is signed, so a prompt injection cannot bypass them.
      MIT

    • x402-btc-radar

      gaodongmei478
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to call pay-per-call x402 endpoints on Base mainnet using the caller's own USDC wallet, covering single and batch token risk checks, the latest BTC radar signal, project info, and a free health probe. Payments are EIP-3009 signed with a configurable per-call spending cap, and any quote with an unexpected payee, network, or asset is refused before payment.
      MIT

    • PayAgent

      Evoarislan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to autonomously pay for metered web APIs on a per-call basis, settling x402 v2 USDC micropayments via EIP-3009 authorization on Base Sepolia without human involvement. Spending is bounded by configurable per-call caps and host restrictions, and exposes tools to fetch paywalled URLs and inspect the agent wallet's address and balance.
      MIT
    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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct action: HTTP fetching, budget inspection, EVM transaction execution, and audit inspection. Although x402_fetch and x402_safe_tx both involve spending controls, their resources and outcomes are clearly separated.

    Naming Consistency4/5

    All tools share the consistent x402_ prefix and use readable snake_case, but the verb pattern is slightly mixed: x402_fetch and x402_get_budget are verb-led, while x402_safe_tx and x402_audit_log are noun/adjective-led. The deviation is minor and still predictable.

    Tool Count5/5

    Four tools is well-scoped for a focused firewall/payment-safety server. Each tool covers a distinct core capability without obvious padding or triviality.

    Completeness4/5

    The surface covers the main lifecycle: safe fetching, budget visibility, safe transaction execution, and audit review. Minor gaps exist around managing or updating spending caps and allowlists, but core firewall workflows are represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources