Skip to content
MCP Server Directory logo
developer-tools

GateCheck

Preflight checks for paid x402 and MCP tools, reporting public metadata, unpaid 402 behavior, request summaries, hashes, and returned artifacts.

Reviewed overview

MCP 服务器概览

what is GateCheck? GateCheck is a hosted remote MCP server and x402 readiness/preflight surface for paid agent-tool sellers. It verifies that paid x402 and MCP tools are discoverable, inspectable, and claim-bounded before public submission, promotion, or paid agent routing.

how to use GateCheck?

  • Endpoint: https://proofbeforepay.vercel.app/gatecheck/mcp (transport: streamable-http). Public introspection endpoints include initialize and tools/list. Some execution calls may require a bearer token.
  • Client config: add the gatecheck MCP server entry (type: streamable-http, url: endpoint) to your mcpServers configuration. If you have a GateCheck token, send Authorization: Bearer YOUR_GATECHECK_TOKEN for protected calls.
  • Interaction: call tools/list and initialize for inspection; use exposed tools for checks and generate launch packs or trust receipts. Do not include private keys, wallet secrets, cookies, or customer data in public metadata.

key features

  • Hosted MCP endpoint with public introspection and optional protected execution
  • Six MCP tools: boundary_guard_check, scan_x402_resource, probe_x402_paid_path, check_agent_tool_readiness, generate_x402_launch_pack, generate_trust_receipt
  • Product and MCP inventory discovery (homepage, llms.txt, agents.txt, product/skill cards, sitemap, MCP server card)
  • x402 unpaid 402 challenge inspection without submitting payments or moving funds
  • Generates launch packs, trust receipts, request summaries, hashes, and returned artifacts
  • Scorecard, product card, and marketplace index for evaluation
  • Pay-by-USDC offers via PayanAgent to automatically return purchased artifacts

use cases

  1. Pre-submission readiness checks before listing a paid tool in a marketplace
  2. Verifying discoverability and inspectability for buyers or agent routing
  3. Generating launch packs and evidence artifacts for marketplace approval workflows
  4. Automated validation for paid-tool vendors to prove observed public metadata and behavior
  5. Quick paid checks (micro-priced) and packaged launch offerings via PayanAgent

FAQ

  • Is GateCheck public or protected?

    Public introspection (initialize, tools/list) is available. Protected tool execution may require a bearer token for production calls.

  • Does GateCheck perform payments or move funds during checks?

    No. GateCheck inspects unpaid 402 behavior and does not submit payment signatures or move funds.

  • What do GateCheck receipts and artifacts prove?

    They prove observed public metadata, unpaid 402 behavior, request summaries, hashes, and returned artifacts only. They do not prove marketplace endorsement, settlement, custody, KYC/AML, security certification, or buyer adoption.

  • How can I purchase a check or launch pack?

    Fixed-price offers are available through PayanAgent (links and prices provided in the project readme). Buyer input is validated before payment; purchased artifacts are returned automatically in USDC.

  • Where can I find documentation and scorecard?

    Product homepage and scorecard links are published (product card, scorecard.md, marketplaces.json) in the repository and on the hosted product site.