Publisher
Conformance
Both modes of conformance/bin/conformance-test, run against the live service immediately before opening this:
registry PASS — 0 critical specification errors and 0 warnings
publisher PASS — 0 critical specification errors and 0 warnings
GET /agents is implemented as a paginated object (items, totalSize, nextPageToken), so the optional endpoint passes rather than returning 404.
What it demonstrates
Offered for the "Implementations in the wild" section (#71) as a worked example of parts of v0.91 that are specified but not yet widely built.
1. federation: auto (§5.4). Concurrent fan-out to the other public registries under a hard time budget, fused with reciprocal rank fusion, with the per-upstream outcome reported in the response so a caller can see which registries actually answered. RRF rather than score fusion because upstream scores are not comparable across registries, and merging on score would import another service's calibration.
2. Both roles from one service. Registry and publisher, with the registry advertised as an application/ai-registry+json entry in its own manifest — the discovery path §5.3 describes.
3. Media-type and URN normalisation. application/mcp-server, application/mcp-server+json and application/mcp-server-card+json are all in circulation across live indexes today, and urn:air: / urn:ai: both appear as discovery-URN prefixes. Because filters match exactly, entries get dropped silently. Neuronto normalises both on ingest, so a filter for MCP servers matches all three spellings:
filter type = application/mcp-server+json -> 10 results
filter type = application/mcp-server -> 10 results
filter type = application/mcp-server-card+json -> 10 results
This may be worth a note in §5.3.1 independently of this implementation, and it relates to #66.
4. Liveness. Indexed endpoints are probed and non-responding ones demoted in ranking rather than deleted, since services come back.
Index
9,626 entries from 5,647 publishers, refreshed continuously from the public ARD registries, the official MCP Registry, and direct crawling of the well-known paths.
Happy to add a row to the table in #71 in whatever shape it settles on, or to answer anything about the federation behaviour.
Publisher
did:web:neuronto.com(resolvable at/.well-known/did.json)Conformance
Both modes of
conformance/bin/conformance-test, run against the live service immediately before opening this:GET /agentsis implemented as a paginated object (items,totalSize,nextPageToken), so the optional endpoint passes rather than returning 404.What it demonstrates
Offered for the "Implementations in the wild" section (#71) as a worked example of parts of v0.91 that are specified but not yet widely built.
1.
federation: auto(§5.4). Concurrent fan-out to the other public registries under a hard time budget, fused with reciprocal rank fusion, with the per-upstream outcome reported in the response so a caller can see which registries actually answered. RRF rather than score fusion because upstream scores are not comparable across registries, and merging on score would import another service's calibration.2. Both roles from one service. Registry and publisher, with the registry advertised as an
application/ai-registry+jsonentry in its own manifest — the discovery path §5.3 describes.3. Media-type and URN normalisation.
application/mcp-server,application/mcp-server+jsonandapplication/mcp-server-card+jsonare all in circulation across live indexes today, andurn:air:/urn:ai:both appear as discovery-URN prefixes. Because filters match exactly, entries get dropped silently. Neuronto normalises both on ingest, so a filter for MCP servers matches all three spellings:This may be worth a note in §5.3.1 independently of this implementation, and it relates to #66.
4. Liveness. Indexed endpoints are probed and non-responding ones demoted in ranking rather than deleted, since services come back.
Index
9,626 entries from 5,647 publishers, refreshed continuously from the public ARD registries, the official MCP Registry, and direct crawling of the well-known paths.
Happy to add a row to the table in #71 in whatever shape it settles on, or to answer anything about the federation behaviour.