Skip to main content

Boundary Guard x402

io.github.LarryLemonBot/boundary-guard-x402Version 0.1.0

MCP tools for x402 readiness, paid-path probes, launch packs, and trust receipts.

Status

Responds174 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:39 UTC
Latency
174 ms
Remotes responding
1 of 1
Sign-in
API key
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://x402-resource-scanner.vercel.app/mcpResponds174 ms
No sign-in

Claude Code

claude mcp add --transport http boundary-guard-x402 https://x402-resource-scanner.vercel.app/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'

Replace <YOUR_TOKEN> before running.

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: boundary-guard-x402
Remote MCP server URL: https://x402-resource-scanner.vercel.app/mcp
This server expects the header Authorization.

Cursor

{
  "mcpServers": {
    "boundary-guard-x402": {
      "url": "https://x402-resource-scanner.vercel.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Replace <YOUR_TOKEN> before running.

VS Code

code --add-mcp '{"name":"boundary-guard-x402","type":"http","url":"https://x402-resource-scanner.vercel.app/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'

Replace <YOUR_TOKEN> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

6 tools

Tools of Boundary Guard x402
Read-only
Idempotent
Open world
boundary_guard_checkCreate a deterministic, read-only pre-action receipt from request, policy, and optional result evidence. Use before an agent posts, spends, lists, or writes so the decision can be audited; no external action is executed.NoYesYesYes
check_agent_tool_readinessGateCheck readiness: check whether an x402/agent-facing tool is ready for agent routing, marketplace listing, and paid-path monitoring, including public agent discovery surfaces (/llms.txt, /agents.txt, /.well-known/mcp.json, /mcp). Pass target plus optional tier, marketplace_url, expected_resources, and paid_path; deep/report tiers add unpaid 402 probing when paid_path is supplied. Tiers: quick $1, deep $5, report $10.NoYesYesYes
generate_trust_receiptGenerate a deterministic trust receipt from sanitized request/policy/result/payment summaries. Do not submit raw auth headers, cookies, API keys, private keys, payment signatures, payment response headers, customer prompts, customer documents, or payer-identifying evidence.NoYesYesYes
generate_x402_launch_packGenerate marketplace-safe launch assets for an x402/MCP seller: listing copy, buyer FAQ, checklist, approval packet, and claim boundaries. Pass target plus optional product_name, audience, primary_use_case, marketplace_url, and paid_path; service/premium tiers include readiness evidence. Tiers: single $9, service $29, premium $49.NoYesYesYes
probe_x402_paid_pathProbe a public x402 paid endpoint without signing or paying, then parse the HTTP 402 challenge. Pass target plus optional expected network/asset/price to verify payment metadata and receive a deterministic health receipt.NoYesYesYes
scan_x402_resourceRead-only scan of a public API/provider URL for x402, OpenAPI, pricing, and agent-discovery metadata. Pass url, and optionally marketplace_url plus expected_resources, to get a readiness score, issues, and fixes; no private endpoints are called.NoYesYesYes

Details

Registry status
Active
Published
May 16, 2026
Updated
May 16, 2026
Repository
Not given
Categories (suggested)
Invoicing and accountingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing