MCP Registry Navigator
Generates MCP client installation snippets and publication checklists for npm packages, helping users publish and install MCP servers distributed through npm.
Generates MCP client installation snippets and publication checklists for PyPI packages, helping users publish and install MCP servers distributed through PyPI.
MCP Registry Navigator
Read-only MCP server for discovering, comparing, and auditing public servers from the official Model Context Protocol Registry.
Serveur MCP en lecture seule pour decouvrir, comparer et auditer les serveurs publics du registre officiel Model Context Protocol.
Overview
MCP Registry Navigator helps agents and developers answer practical questions before installing or publishing an MCP server:
Which MCP server fits a task best?
What package registry, transport, and install command does it use?
Is a
server.jsonfile ready for registry publication?What checklist should be followed before publishing a PyPI, npm, or OCI MCP server?
The server does not edit user files. It returns structured reports, generated configuration snippets, and review checklists that callers can inspect and apply manually.
Related MCP server: MCP Registry Server
Vue d'ensemble
MCP Registry Navigator aide les agents et les developpeurs a prendre de bonnes decisions avant d'installer ou de publier un serveur MCP :
Quel serveur MCP convient le mieux a une tache donnee ?
Quel registre de package, transport et commande d'installation utilise-t-il ?
Un fichier
server.jsonest-il pret pour une publication dans le registre ?Quelle checklist suivre avant de publier un serveur MCP via PyPI, npm ou OCI ?
Le serveur ne modifie aucun fichier utilisateur. Il retourne des rapports structures, des snippets de configuration et des checklists que l'appelant peut relire puis appliquer manuellement.
Features / Fonctionnalites
Search latest servers from
https://registry.modelcontextprotocol.io.Fetch a specific server by registry name and version.
Compare server package types, transports, and descriptions.
Validate
server.jsonmetadata before publication.Generate MCP client install snippets for PyPI, npm, and OCI packages.
Prepare publication checklists for PyPI, npm, and OCI registry flows.
Expose MCP tools, resources, and prompts through the official Python SDK v2.
Use a local TTL JSON cache and deterministic test fixtures.
MCP Primitives
Tools
search_serversget_servercompare_serversvalidate_server_jsongenerate_install_configprepare_publish_checklist
Resources
registry://servers/{name}registry://latestregistry://cache/status
Prompts
choose_mcp_serveraudit_mcp_metadataprepare_mcp_release
Requirements / Prerequis
Python 3.12 or newer.
uvfor local Python dependency management.Node.js 22.19.0 or newer only when using the MCP Inspector.
Installation
From a local checkout:
uv sync
uv run mcp-registry-navigator --versionDepuis un clone local :
uv sync
uv run mcp-registry-navigator --versionUsage
Run over stdio, the default transport for local MCP clients:
uv run mcp-registry-navigatorLancer le serveur en stdio, le transport par defaut pour les clients MCP locaux :
uv run mcp-registry-navigatorRun as Streamable HTTP for local testing:
uv run mcp-registry-navigator --transport streamable-http --host 127.0.0.1 --port 8000Lancer le serveur en Streamable HTTP pour les tests locaux :
uv run mcp-registry-navigator --transport streamable-http --host 127.0.0.1 --port 8000Run the MCP Inspector:
npm install
npm run inspectLancer le MCP Inspector :
npm install
npm run inspectThis repository includes .node-version and package.json so local inspection
uses @modelcontextprotocol/inspector v2 instead of the deprecated v1 launcher
used by some mcp dev environments.
Ce depot inclut .node-version et package.json afin que l'inspection locale
utilise @modelcontextprotocol/inspector v2 au lieu de l'ancien lanceur v1
utilise par certains environnements mcp dev.
Example Client Config
For a local checkout:
{
"mcpServers": {
"mcp-registry-navigator": {
"command": "uv",
"args": [
"--directory",
"/path/to/mcp-registry-navigator",
"run",
"mcp-registry-navigator"
]
}
}
}After publishing to PyPI, the command can be simplified:
{
"mcpServers": {
"mcp-registry-navigator": {
"command": "uvx",
"args": ["mcp-registry-navigator"]
}
}
}Development / Developpement
uv run python -m pytest -q
uv run ruff check .
uv run mypy
uv build
npm run inspectThe test suite uses fake registry responses for deterministic offline coverage. The MCP integration tests use the SDK in-memory client and do not open ports.
La suite de tests utilise de fausses reponses du registre pour rester deterministe et fonctionner hors ligne. Les tests d'integration MCP utilisent le client en memoire du SDK et n'ouvrent pas de port reseau.
Cache
The default cache file is:
~/.cache/mcp-registry-navigator/registry-cache.jsonSet XDG_CACHE_HOME to change the cache root. Use NullCache in tests or
embedding code when no disk writes are desired.
Le fichier de cache par defaut est :
~/.cache/mcp-registry-navigator/registry-cache.jsonDefinissez XDG_CACHE_HOME pour changer la racine du cache. Utilisez
NullCache dans les tests ou dans du code embarque si aucune ecriture disque ne
doit etre effectuee.
Repository Status / Etat du depot
This project is currently alpha software. APIs and generated recommendations may change while the MCP Registry and Python SDK continue to evolve.
Ce projet est actuellement en phase alpha. Les APIs et les recommandations generees peuvent changer pendant que le registre MCP et le SDK Python evoluent.
Release Notes / Notes de publication
Before publishing to PyPI, add [project.urls] in pyproject.toml with the
real GitHub repository URL and issue tracker.
Avant une publication sur PyPI, ajoutez [project.urls] dans pyproject.toml
avec l'URL reelle du depot GitHub et le lien vers le suivi des issues.
If later publishing this server to the official MCP Registry as a PyPI package, add the registry verification marker to this README:
<!-- mcp-name: io.github.YOUR_GITHUB_USERNAME/mcp-registry-navigator -->Si ce serveur est ensuite publie dans le registre MCP officiel comme package PyPI, ajoutez le marqueur de verification ci-dessus dans ce README.
License / Licence
MIT. See LICENSE.
Available Tools
6 toolscompare_serversCompare MCP ServersARead-only
Compare package types, transports, and summaries for MCP servers.
Inputs: names (required). Returns: object
generate_install_configGenerate install configBRead-only
Generate an MCP client configuration snippet for one server.
Inputs: server_json (required). Returns: object
get_serverGet MCP Registry ServerARead-only
Fetch one MCP Registry server metadata record.
Inputs: name (required), version. Returns: object
prepare_publish_checklistPrepare publish checklistBRead-only
Return a publication readiness checklist for a server.json file.
Inputs: server_json (required). Returns: object
search_serversSearch MCP RegistryCRead-only
Search latest public MCP Registry server metadata.
Inputs: limit, query. Returns: object
validate_server_jsonValidate server.jsonARead-only
Validate MCP Registry server.json metadata without publishing it.
Inputs: server_json (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool performs a distinct operation: search, fetch, compare, validate, generate config, and checklist. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern (search_servers, get_server, compare_servers, validate_server_json, generate_install_config, prepare_publish_checklist), making them predictable and easy to parse.
With 6 tools, the set is well-scoped for a registry navigator and pre-publish helper. Each tool covers a necessary step in browsing, validating, and preparing server configurations without excess.
The tool surface covers search, retrieval, comparison, validation, config generation, and publication readiness. A direct publish tool is missing, but that may be intentionally outside the 'navigator' scope, so the gap is minor.
Maintenance
Related MCP Connectors
Publish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.
The MCP server that finds MCP servers. Aggregates Official Registry, Glama, and Smithery.
Search the public universe of MCP servers. This data comes from the Official MCP Registry.
Search the official MCP registry: 17,000+ servers with trust grades, stars, tools, install config.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving detailed information about MCP servers from the official MCP registry. Provides tools to list servers with filtering options and get comprehensive details about specific servers.48 npm3MIT
- AlicenseBqualityDmaintenanceEnables discovery and search of available MCP servers through the official MCP Registry. Supports browsing servers with pagination and filtering to find the right MCP tools for your needs.145 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables discovery and querying of available MCP servers from the official repository. Supports searching by name, description, features, categories, and provides random server suggestions for exploration.17 npm3MIT
- AlicenseAqualityDmaintenanceEnables searching the official MCP Registry for servers, inspecting details, and generating install commands directly from within an agent session.4MIT