io.github.OnticX/open-mcp-registry
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_REGISTRY_BASE_URL | No | Public base URL of the registry (optional, defaults to localhost) | |
| MCP_REGISTRY_SEED_FROM | No | Path to seed data file (optional, e.g., data/seed.json) | |
| MCP_REGISTRY_DATABASE_URL | Yes | PostgreSQL connection string (e.g., postgres://user:pass@host:5432/registry) | |
| MCP_REGISTRY_SESSION_SECRET | No | Session secret for authentication cookies (optional, recommended) | |
| MCP_REGISTRY_GITHUB_CLIENT_ID | No | GitHub OAuth client ID (optional, required for publishing) | |
| MCP_REGISTRY_GITHUB_CLIENT_SECRET | No | GitHub OAuth client secret (optional, required for publishing) | |
| MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION | No | Enable validation on seed data (optional, defaults to true) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_mcp_registryA | Search the MCP Tool Registry for available servers and tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of ambiguity or overlap. The purpose is clear and singular.
With a single tool named 'open_mcp_registry', the naming follows a consistent snake_case style. There is no mixed convention to cause inconsistency.
The server has only one tool, which feels thin for a registry service. While a search tool is core, one tool borders on minimalism and could benefit from additional operations like listing or metadata retrieval.
The tool provides search functionality over the MCP registry, which covers the primary need. Minor gaps exist, such as no direct retrieval by name or browsing capabilities, but the core search use case is addressed.