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)

MCP servers are addressable by W3C DIDs. DIDs enable verification of controller keys and rotation over time without centralized registries.

2) Attestations (Verifiable Credentials)

VCs describe verifiable facts: ownership, hosting environment, audit status, assurance level, allowed capabilities, and compliance certifications.

3) Registry & Discovery

Trust registries list servers, manifests, issuers, and revocations — enabling clients to discover and filter by policy requirements.

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 use for endpoints, certificates, and software supply chains — but for AI tools.

Where the Standard Lives

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

Core Repositories
📘 Specification (SSOT) 🔐 DID/VC Infrastructure 📛 Agent Name Service 📋 Trust Registry 🔄 A2A Delegation
SDKs & Tools
🐍 Python SDK 📘 TypeScript SDK 💡 Examples ⚡ Quickstarts
Want to contribute? Start with issues and pull requests. Keep changes backward-compatible whenever possible — stability is a feature.