Categories › AI & Agents › Multi-agent, orchestration & workflows
Surface contracts: API behavior evidence, x402 pre-payment check, MCP server preflight
Remote server: your requests and data go to penny-surface-contract.penny-mcamp.workers.dev. Claude Code: claude mcp add --transport http surface-contract-platform-api-behavior-a https://penny-surface-contract.penny-mcamp.workers.dev/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
list_surface_contracts — List the platform surface contracts published in Penny's free registry, with claim counts.get_surface_contract — Get the machine-readable surface contract for a platform host (read/write semantics, pending states, rate limits, limits, idempotency, paginverify_surface — Run the anonymous conformance checks for a contract now and return verified / failed / unknown / manual / unsupported per claim.contribute_discrepancy — Report a platform behaviour that contradicts a published claim, or a new claim, with evidence. One-line call: POST /v1/contribute with {contget_integration_recipe — Get a plain-text integration recipe for a platform: the order of operations to use it, and a guard clause for every behaviour we measured gopreflight_mcp_server — Run the anonymous MCP handshake against ANY https MCP endpoint you name, right now, and get back a verdict (open / refused / unreachable / iprepay_check — Check an x402 route BEFORE you pay it. GET /v1/prepay?url=<the route> makes ONE unpaid GET with no payment header and no credential, and retNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.