mcp-registry-finder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_REGISTRY_FINDER_BASE_URL | No | Override the base URL of the official MCP registry API (default: https://registry.modelcontextprotocol.io/v0) | https://registry.modelcontextprotocol.io/v0 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_registryA | Search the official Model Context Protocol registry (registry.modelcontextprotocol.io) for published MCP servers by substring match on name. Returns matching servers with version, status, and description. |
| get_server_detailsA | Fetch full details for one MCP server from the official registry by its reverse-DNS name (e.g. 'io.github.user/weather'), including install packages, required environment variables, and remote endpoints. |
| list_recent_serversA | List MCP servers from the official registry, optionally filtered to those updated within the last N days. Useful for spotting newly published servers. |
| format_install_commandA | Offline helper: given a package registryType (npm, pypi, oci, nuget, cargo, mcpb) and identifier, return the runnable install/launch command. Does not contact the network. |
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 4 tools
Each tool has a clearly distinct purpose: format_install_command converts registry types to install commands, get_server_details fetches details by name, list_recent_servers lists recent servers, and search_registry searches by substring. No overlap.
All tool names follow a consistent verb_noun pattern (format_install_command, get_server_details, list_recent_servers, search_registry). No mixing of conventions.
With 4 tools, the set is well-scoped for a registry finder server. Each tool serves a distinct need without unnecessary bloat or gaps.
The tool set covers the main workflows: searching, listing recent, getting details, and generating install commands. No obvious dead ends or missing operations for the domain.