Skip to content
Back to search

registry

A community driven registry service for Model Context Protocol (MCP) servers.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/modelcontextprotocol/registry with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/modelcontextprotocol/registry'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/modelcontextprotocol--registry/badge.svg)](/listings/modelcontextprotocol--registry)

HTML

<a href="/listings/modelcontextprotocol--registry"><img src="/api/listings/modelcontextprotocol--registry/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Pre-requisites

- **Docker** - **Go** - version per the `go` directive in [go.mod](./go.mod); the Go toolchain fetches it for you - **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/)) - **golangci-lint** - version per the `golangci-lint-action` pin in [ci.yml](./.github/workflows/ci.yml), so local lint matches CI

Running the server

# Start full development environment
make dev-compose

This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.

**Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.

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 with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.

The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.

<details> <summary>Alternative: Running a pre-built Docker image</summary>

Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via `MCP_REGISTRY_DATABASE_URL` (see [docker-compose.yml](./docker-compose.yml) for a working example):

# 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

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

</details>

Publishing a server

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

See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.

Other commands

# Run lint, schema validation, and all tests
# Note: this also runs `make dev-down`, stopping any running dev-compose environment
make check

There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 158 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # MCP Registry
  2. The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
  3. [**📤 Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚡️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**👀 Ecosystem vision**](docs/design/ecosystem-vision.md) | 📖 **[Full documentation](./docs)**
  4. ## Development Status
  5. **2025-10-24 update**: The Registry API has entered an **API 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!
  6. **2025-09-08 update**: The registry has launched in preview 🎉 ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
  7. Registry Working Group:
  8. - **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov) - WG Lead
  9. - **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
  10. - **Bob Dickinson** (TeamSpark) [@BobDickinson](https://github.com/BobDickinson)
  11. - **Preeti (Pree) Dewani** (Ravenmail) [@pree-dew](https://github.com/pree-dew)
  12. ## Contributing
  13. We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
  14. Often (but not always) ideas flow through this pipeline:
  15. - **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
  16. - **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
  17. - **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work
  18. - **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
  19. ### Quick start:
  20. #### Pre-requisites
  21. - **Docker**
  22. - **Go** - version per the `go` directive in [go.mod](./go.mod); the Go toolchain fetches it for you
  23. - **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
  24. - **golangci-lint** - version per the `golangci-lint-action` pin in [ci.yml](./.github/workflows/ci.yml), so local lint matches CI
  25. #### Running the server
  26. ```bash
  27. # Start full development environment
  28. make dev-compose
  29. ```
  30. This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
  31. **Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
  32. 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 with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
  33. The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
  34. <details>
  35. <summary>Alternative: Running a pre-built Docker image</summary>
  36. Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via `MCP_REGISTRY_DATABASE_URL` (see [docker-compose.yml](./docker-compose.yml) for a working example):
  37. ```bash
  38. # Run latest stable release
  39. docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
  40. # Run latest from main branch (continuous deployment)
  41. docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
  42. # Run specific release version
  43. docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
  44. # Run development build from main branch
  45. docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
  46. ```
  47. **Available tags:**
  48. - **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
  49. - **Continuous**: `main` (latest main branch build)
  50. - **Development**: `main-<date>-<sha>` (specific commit builds)
  51. </details>
  52. #### Publishing a server
  53. Publishing an MCP server does **not** happen through a pull request to this repository. Adding a `server.json`, a server directory, or an entry in `data/seed.json` will not publish or list your server, even if the PR is merged. Use the `mcp-publisher` CLI from your server's own project instead.
  54. To publish a server, we've built a simple CLI. You can use it with:
  55. ```bash
  56. # Build the latest CLI
  57. make publisher
  58. # Use it!
  59. ./bin/mcp-publisher --help
  60. ```
  61. See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
  62. #### Other commands
  63. ```bash
  64. # Run lint, schema validation, and all tests
  65. # Note: this also runs `make dev-down`, stopping any running dev-compose environment
  66. make check
  67. ```
  68. There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
  69. <!--
  70. For Claude and other AI tools: Always prefer make targets over custom commands where possible.
  71. -->
  72. ## Architecture
  73. ### Project Structure
  74. ```
  75. ├── cmd/ # Application entry points
  76. │ ├── publisher/ # Server publishing tool
  77. │ └── registry/ # Registry API server
  78. ├── data/ # Seed data
  79. ├── deploy/ # Deployment configuration (Pulumi)
  80. ├── docs/ # Documentation
  81. ├── internal/ # Private application code
  82. │ ├── api/ # HTTP handlers and routing
  83. │ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)
  84. │ ├── config/ # Configuration management
  85. │ ├── database/ # Data persistence (PostgreSQL)
  86. │ ├── importer/ # Seed data import
  87. │ ├── service/ # Business logic
  88. │ ├── telemetry/ # Metrics and monitoring
  89. │ └── validators/ # Input validation
  90. ├── pkg/ # Public packages
  91. │ ├── api/ # API types and structures
  92. │ │ └── v0/ # Version 0 API types
  93. │ └── model/ # Data models for server.json
  94. ├── scripts/ # Development and testing scripts
  95. ├── tests/ # Integration tests
  96. └── tools/ # CLI tools and utilities
  97. └── validate-*.sh # Schema validation tools
  98. ```
  99. ### Authentication
  100. Publishing supports multiple authentication methods:
  101. - **GitHub OAuth** - For publishing by logging into GitHub
  102. - **GitHub OIDC** - For publishing from GitHub Actions
  103. - **DNS verification** - For proving ownership of a domain and its subdomains
  104. - **HTTP verification** - For proving ownership of a domain
  105. The registry validates namespace ownership when publishing. E.g. to publish...:
  106. - `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
  107. - `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
  108. ## Community Projects
  109. Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
  110. ## More documentation
  111. See the [documentation](./docs) for more details if your question has not been answered here!

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.