Registry Expansion Routing
mcp remote · streamable-http · v1.0.0 · source: crawl
https://bonissystems.com/api/knox/agents/registry-expansion/mcp
Public-registry routing map by entity kind. Read-only reference data, not a determination.
Works
100
Verified Oct 31, 2026 · p50 580 ms · p95 623 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'knox-registry-expansion' |
| tools_listed | 15 | pass | 1 tools |
| schema_complete | 15 | pass | 1 of 1 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 580 ms |
| latency_p95 | 5 | pass | p95 623 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (1)
| Name | Description | Schema |
|---|---|---|
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 | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/com-bonissystems-registry-expansion)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.