registry-tools
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REGISTRY_URL | No | mpak registry URL | https://registry.mpak.dev |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| registry_searchA | Search the mpak registry for available MCP servers. Returns name, description, tools, version, and verification status. |
| registry_resolveA | Get full metadata for a specific package from the mpak registry. Includes credential requirements and available tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| registry_tools_skill | How to effectively use registry tools. |
TDQS
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.