SnapState

2025-10-24 update: The Registry API has entered anAPI freeze (v0.1)🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!

Often (but not always) ideas flow through this pipeline:

# Start full development environment make dev-compose

By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation withMCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.

Pre-built Docker images are automatically published to GitHub Container Registry:

# Run latest stable release docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest # Run latest from main branch (continuous deployment) docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main # Run specific release version docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0 # Run development build from main branch docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d

- Releases:latest,v1.0.0,v1.1.0, etc.
- Continuous:main(latest main branch build)
- Development:main-<date>-<sha>(specific commit builds)

To publish a server, we've built a simple CLI. You can use it with:

# Build the latest CLI make publisher # Use it! ./bin/mcp-publisher --help

# Run lint, unit tests and integration tests make check

├── cmd/ # Application entry points │ └── publisher/ # Server publishing tool ├── data/ # Seed data ├── deploy/ # Deployment configuration (Pulumi) ├── docs/ # Documentation ├── internal/ # Private application code │ ├── api/ # HTTP handlers and routing │ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking) │ ├── config/ # Configuration management │ ├── database/ # Data persistence (PostgreSQL) │ ├── service/ # Business logic │ ├── telemetry/ # Metrics and monitoring │ └── validators/ # Input validation ├── pkg/ # Public packages │ ├── api/ # API types and structures │ │ └── v0/ # Version 0 API types │ └── model/ # Data models for server.json ├── scripts/ # Development and testing scripts ├── tests/ # Integration tests └── tools/ # CLI tools and utilities └── validate-*.sh # Schema validation tools

Publishing supports multiple authentication methods:

- GitHub OAuth- For publishing by logging into GitHub
- GitHub OIDC- For publishing from GitHub Actions
- DNS verification- For proving ownership of a domain and its subdomains
- HTTP verification- For proving ownership of a domain

The registry validates namespace ownership when publishing. E.g. to publish...:

- io.github.domdomegg/my-cool-mcpyou must login to GitHub asdomdomegg, or be in a GitHub Action on domdomegg's repos
- me.adamjones/my-cool-mcpyou must prove ownership ofadamjones.mevia DNS or HTTP challenge

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

What Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.

CodeVF MCP lets AI hand off problems to real engineers instantly, so your workflows don’t stall when models hit their limits.

Client implementation for Mastra, providing seamless integration with MCP-compatible AI models and tools.

Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.

On-demand access to 150+ specialist AI agent templates — search, browse, and spawn agents. 150x reduction in context usage vs loading agents locally.

AgentChatBus is a persistent AI communication bus that lets multiple independent AI Agents chat, collaborate, and delegate tasks — across terminals, across IDEs, and across frameworks.

Remote MCP server (Streamable HTTP) at https://mcp.agenticrail.nz/ — deterministic step-order enforcement for AI agents. evaluate_step returns ALLOW or DENY before a step runs; verify_receipt proves a sequence's Ed25519-signed, hash-chained receipt chain is intact. No auth required: omit the bearer token and calls run on the public demo key. That first clause matters — the form has no "remote/hosted" field, and putting the endpoint in the description is the convention on that list ("Fully REMOTE! Just use…"). The rest mirrors your own server card verbatim, so the listing and the card can't drift.

An AI Agent with optional Human-in-the-Loop Safety and Model Context Protocol (MCP) integration.

Agent Mail Rooms is a paid remote MCP endpoint for OpenAI Codex agent coordination MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-