Boundary Guard X402
Verify x402 paid endpoints, agent-tool readiness, and trust receipts before you list or wire paid MCP tools into Claude Code or Cursor.
Overview
Boundary Guard x402 is an MCP server for the Ship phase that scans x402 resources, probes paid paths safely, and generates launch packs and trust receipts for agent-tool monetization.
What is this MCP server?
- Six MCP tools: boundary_guard_check, scan_x402_resource, probe_x402_paid_path, check_agent_tool_readiness, generate_x402
- SSRF policy blocks private, internal, credentialed, and unsafe probe targets before any call runs
- Public MCP discovery with bearer auth on protected tool execution via marketplace or operator tokens
- OpenAPI and llms.txt discovery at x402-resource-scanner.vercel.app for agent-friendly integration
- Data policy: no private keys, API keys, cookies, or raw payment response headers in submissions
- 6 named MCP tools in publisher metadata
- OpenAPI at x402-resource-scanner.vercel.app/openapi.json
- Category: Agent Verification and Security (LarryBuildsAI)
What problem does it solve?
You are about to ship paid x402 or MCP tools but lack a safe, standardized way to prove readiness and document trust without leaking secrets into probes.
Who is it for?
Indie builders listing x402-backed MCP tools who need automated readiness scans, paid-path probes, and audit-friendly receipts before launch.
Skip if: Teams that only need generic OWASP scanning with no x402 or agent-marketplace context, or anyone unwilling to use bearer auth for protected tool calls.
What do I get? / Deliverables
After registering the server, your agent can run SSRF-guarded checks and produce launch packs and trust receipts you can attach to marketplace listings or internal runbooks.
- x402 readiness and agent-tool readiness reports
- Generated x402 launch packs and trust receipts for listings
- Evidence from scan_x402_resource and probe_x402_paid_path without unsafe SSRF targets
Recommended MCP Servers
Journey fit
How it compares
x402-focused verification MCP server, not a general code-review skill or payment processor.
Common Questions / FAQ
Who is Boundary Guard X402 for?
Solo and indie builders shipping paid MCP or x402 agent tools who want LarryBuildsAI’s verification tools inside Claude Code, Cursor, or other MCP clients before marketplace launch.
When should I use Boundary Guard X402?
Use it during ship/security when you have candidate x402 URLs or MCP seller endpoints and need readiness checks, safe paid-path probes, launch pack generation, or trust receipts—not for ad-hoc browsing of private networks.
How do I add Boundary Guard X402 to my agent?
Add the io.github.LarryLemonBot/boundary-guard-x402 MCP entry from the registry, use public discovery at the canonical scanner URL, and configure upstream bearer authorization for protected tools/call as documented by the publisher.