Surface Contract: how platform APIs really behave

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as dev.workers.penny-mcamp.penny-surface-contract/surface-contract and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 14 Oct 2026. Not supplied by the maker.

• 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, pagination completeness, data portability), each claim carrying i

• verify_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. Stored as pending; a published contract is never changed without independent verification.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.