Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index MCP server

Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index

One search across every public ARD registry, plus a verified index of what MCP servers actually expose.

neuronto.com · API · Submit your server · Benchmark · Dataset · Manifest

What is ARD?

ARD is short for Agentic Resource Discovery, an open specification for how AI agents find the tools, skills, agents and APIs they need, published in June 2026 by a working group including Google, Microsoft, Hugging Face, AWS, Cisco, GitHub, Nvidia, Salesforce and Snowflake.

An agentic resource is anything an AI client can call to get work done: an MCP server, an A2A agent, a skill, an API, a workflow.

ARD answers one question, "what is available for this task?", and then gets out of the way. It is not a runtime and does not replace MCP or A2A. It tells an agent what exists; the agent connects using the resource's own protocol.

The problem it solves

Today an agent can only use capabilities someone installed for it in advance. Every tool has to be wired in by hand, and every tool description has to sit in the context window, competing for space with the actual work. That model does not survive contact with an ecosystem of thousands of tools, let alone millions.

ARD moves the selection problem out of the context window and into a search service, the same shift the early web made when it went from curated link directories to search engines.

For that to work, two sides have to exist. Publishers describe what they offer at a well-known location on their own domain. Registries index those descriptions and answer queries. Neuronto is both.

Why a federated index

The specification defines three federation modes and makes auto the default: a registry queries its peers, merges their results, and returns one set.

In practice each public registry answers only from its own catalogue, so the same question asked in four places returns four different answers and the client has to pick a side. That is the problem Neuronto exists to remove.

Ask Neuronto once and the query fans out across every public ARD registry concurrently. Results are fused with reciprocal rank fusion, which combines the orderings rather than the scores, necessary because each registry calibrates differently, and importing another service's scoring would import its biases with it.

The response says which registries answered and which timed out, so a caller always knows how much of the federation is behind an answer.

What it does differently

Federated by default. federation: auto implemented as specified: concurrent fan-out under a hard time budget, fused ranking, per-upstream reporting. A slow peer costs the budget and nothing more.

Complete conformance. Passes the specification's official conformance tool as both a registry and a publisher with zero errors and zero warnings, including the optional GET /agents listing as a properly paginated object.

Type normalisation. Three media types for MCP servers are in circulation (application/mcp-server, application/mcp-server+json, application/mcp-server-card+json) and two URN prefixes appear as discovery identifiers (urn:air: and urn:ai:). Because filters match exactly, entries get dropped silently. Neuronto normalises both on ingest, so a filter for MCP servers returns them however the publisher spelled the type.

Shortened. The full README is on GitHub.