Multiple visibility modes
Publish publicly, privately to an organization, or through an unlisted reference.
Supply plane
Know exactly what enters your MCP estate.
Register and inspect tenant-scoped MCP server definitions now, with artifact signing, sharing, compatibility evidence, and revocation planned.
Product boundary
The current registry preview tracks server metadata and version pins. It does not yet provide a complete artifact or skill lifecycle.
- Available now
- Behavior backed by the current local vertical slice and automated tests.
- Preview
- Useful implementation exists, but the complete operating journey is not proven.
- Planned
- Part of the open MCP-native roadmap, not current product behavior.
- Deployment
- Managed cloud and self-hosted targets share portable packages; live parity remains an acceptance test.
Capabilities
What registry controls
Status labels distinguish tested behavior from useful previews and the open roadmap.
Pinned server definitions
Register semantic version metadata and pin compositions to an explicit upstream version.
Compatibility evidence
Attach protocol, client, authentication, and schema test results to each release.
Artifact revocation
Block a compromised version or publisher without waiting for every client to update.
Operating flow
The target journey, with current maturity called out above.
Inspect
Probe capabilities, required scopes, source metadata, and transport support.
Verify
Run compatibility and security checks against a declared release artifact.
Distribute
Install, fork, share, or revoke the artifact through explicit policy.
Target control surface
Designed for platform and security teams.
These controls define the intended product boundary; the capability labels above are the current implementation record.
- Publisher identity
- License and source metadata
- Signed release checksums
- Security notices
- Fork and install lineage
- Organization allowlists
Evaluate locally or inspect either deployment target.
The managed cloud and Kubernetes paths are previews of one open codebase, with no intended capability gate or mandatory call-home path.