Standard

MCPF Standard

The MCPF standard defines a practical trust vocabulary for MCP ecosystems: identities, issuers, credentials, registries, and revocation.

Core concepts

1) Server identity (DID)

An MCP server is addressable by a DID. DIDs enable verification of controller keys and rotation over time.

2) Attestations (Verifiable Credentials)

VCs describe facts you can rely on: ownership, hosting environment, audit status, assurance level, “allowed capabilities”, and more.

3) Registry & discovery

A registry lists servers, manifests, issuers, and revocations — allowing clients to discover and filter by policy.

4) Revocation & deprecation

Trust must be reversible. The framework includes patterns for revoking credentials and marking servers as deprecated or blocked.

Design goal: enforce the same operational hygiene enterprises already use for endpoints, certificates, and software supply chains — but for AI tools.

Where the “standard” lives

The authoritative spec is maintained in GitHub repositories under the MCPTrustFramework organization.

MCPTrustFramework on GitHub Registry model & endpoints Reference tooling
Want to contribute? Start with issues and pull requests, and keep changes backward-compatible whenever possible — stability is a feature.