Boundary Guard x402

io.github.LarryLemonBot/boundary-guard-x402 · v0.1.0 · crypto-web3

Boundary Guard x402 is healthy: it completed an MCP handshake in 2283 ms and exposes 6 tools.

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

Endpoint: https://x402-resource-scanner.vercel.app/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count6
Latency2283 ms
Last checked (UTC)2026-10-15T01:50:40.043Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T01:50:40.043ZHealthy2283

Tools (6)

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.
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.
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.
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
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: sing
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.