io.github.LarryLemonBot/gatecheck

GateCheck by LarryBuildsAI

One-cent x402 and MCP readiness checks plus fixed-price marketplace launch packs.

0.1.3
Version
remote
Transport
6
Tools

Security review

Review passed

Reviewed Jan 1, 2000.

  • tools: 6 tools scanned
  • metadata: scanned

No findings.

Tools (6)

  • boundary_guard_check

    Create 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_resource

    Read-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_path

    Probe 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_readiness

    GateCheck 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.

  • generate_x402_launch_pack

    Generate 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.

  • generate_trust_receipt

    Generate 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.