Public-registry routing map by entity kind. Read-only reference data, not a determination.
Connect Remote server
claude mcp add --transport http registry-expansion https://bonissystems.com/api/knox/agents/registry-expansion/mcp
{
"mcpServers": {
"registry-expansion": {
"url": "https://bonissystems.com/api/knox/agents/registry-expansion/mcp"
}
}
}
{
"servers": {
"registry-expansion": {
"type": "http",
"url": "https://bonissystems.com/api/knox/agents/registry-expansion/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://bonissystems.com/api/knox/agents/registry-expansion/mcp
Tools 1 found in our last check
describe_routingReturn 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.
Details
| Endpoint | https://bonissystems.com/api/knox/agents/registry-expansion/mcp (Streamable HTTP) |
| First published | 24 Jun 2026 |
| Last updated | 24 Jun 2026 |
| Registry name | com.bonissystems/registry-expansion |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
