Four bounded tools
Each tool performs one concrete public task. There is no generic tool able to browse internal routes, execute code or modify an origin.
Public read-only MCP
A common channel for consulting public evidence without taking control.
The deployed MCP server exposes audit, methodology, Registry and OKF through small tools and versioned resources. It is stateless and has no access to owner information.
Inspect the public MCPVersioned resources
Capabilities, methodology, OKF and readiness use stable identifiers. Arbitrary paths and private parameters are rejected.
Verifiable boundaries
The server needs no OAuth because it protects no private data; it also keeps no memory, writes no data, deploys no changes, charges no money and never acts for an owner.
Visible boundaries
- This MCP only reads information that is already public.
- Owner Live and authenticated operations belong to a different boundary.