Registry Expansion Routing
Public-registry routing map by entity kind. Read-only reference data, not a determination.
Should I use this
Quality & Safety
B
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~78Tokens (tool definitions)
~186 BTypical response size
Minimal attention impact (0.06% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"registry-expansion": {
"url": "https://bonissystems.com/api/knox/agents/registry-expansion/mcp"
}
}
}Remote endpoints
https://bonissystems.com/api/knox/agents/registry-expansion/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡describe_routing
Return the registry routing map: for each entity kind, the set of public registries the expansion agent would consult. Pure, local, no input, no PII. Use it to understand coverage before requesting an (authenticated) expansion.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Community
Evidence
Recent observations
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools