Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@registry-tools search for MCP servers related to finance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Search and resolve MCP server packages on the mpak registry. This server lets agents discover available MCP servers, inspect their tools, and check credential requirements before installation.
This is one of the core MCP servers that powers NimbleBrain's agent runtime, giving agents self-service access to the registry. It's open source so you can see how it works, fork it to connect to your own registry, or use it as a reference for building discovery-layer MCP servers.
mpak install @nimblebraininc/registry-toolsclaude mcp add registry-tools -- mpak run @nimblebraininc/registry-tools{
"mcpServers": {
"registry-tools": {
"command": "mpak",
"args": ["run", "@nimblebraininc/registry-tools"]
}
}
}Related MCP server: agentalmanac-mcp
Search the mpak registry for available MCP servers.
Parameter | Type | Required | Description |
|
| Yes | Search term (e.g., "weather", "pdf", "finance") |
Returns matching packages with name, description, tools, download count, and verification status.
Get full metadata for a specific package, including credential requirements and version history.
Parameter | Type | Required | Description |
|
| Yes | Package identifier (e.g., "@nimblebraininc/finnhub") |
|
| No | Specific version (omit for latest) |
Returns detailed package info including tools, required credentials, license, and homepage.
Env Var | Required | Description |
| No | mpak registry URL (default: |
Want to adapt this for your own infrastructure?
Point REGISTRY_URL at your own registry endpoint
Add a registry_browse tool that lists categories or popular servers
Add tools that combine search with automatic installation via your orchestrator
Fork and modify src/mcp_registry_tools/server.py
git clone https://github.com/NimbleBrainInc/mcp-registry-tools.git
cd mcp-registry-tools
# Install dependencies
uv sync --group dev
# Run all checks (format, lint, typecheck, tests)
make check
# Run the server locally (stdio)
uv run python -m mcp_registry_tools.server
# Run the server locally (HTTP)
make run-httpMIT
Get full metadata for a specific package from the mpak registry.
Includes credential requirements and available tools.
Inputs: package (required), version. Returns: object
Search the mpak registry for available MCP servers.
Returns name, description, tools, version, and verification status.
Inputs: query (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have distinct purposes: registry_search is for discovering packages via query, while registry_resolve fetches detailed metadata for a known package. They could be confused if users expect search to return full details, but descriptions clarify the difference.
Both tool names follow a consistent pattern: 'registry_' prefix plus a verb (search, resolve). This makes the naming predictable and easy to navigate.
With only 2 tools, the set feels thin for a registry service, which typically includes list, publish, or management operations. However, for a read-only lookup/query server, this minimal set may be intentionally scoped.
The tools cover search and detailed lookup, but lack obvious operations like listing all packages, publishing new ones, or updating existing registrations. Depending on the intended use case, this may be acceptable but leaves gaps for broader registry management.
Search and get install details on MCP servers, right from your agent -- a unified marketplace index.
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Find an MCP server for any task: searches the official registry, Smithery and npm; remote-first.
Search and inspect source-pinned agent skills, plugins and tools through a free public MCP.
