Agent registries and discovery: how enterprises catalog agents

Updated 18 November 2026 · Editorial assessment

How does an agent find another agent in A2A?

The specification lists discovery among its key goals, so that agents can dynamically find and understand the capabilities of other agents. See the A2A protocol overview for the rest of the protocol.

The card usually sits at a well-known path. Amazon Bedrock AgentCore Runtime preserves built-in agent discovery through Agent Cards at /.well-known/agent-card.json while adding SigV4 or OAuth 2.0 authentication. When you register an external A2A agent with Foundry, Foundry discovers your agent card at the same path and generates a proxy URL.

Some cards are behind authentication, and clients have to handle that. For a Foundry agent target, Microsoft tells you not to set a card path, because Foundry resolves the default agent card path and negotiates the protocol version. For other endpoints that protect their card, you set send_credentials_for_agent_card to true in the A2A tool definition. A direct fetch only reaches agents whose address you already have. A registry tells you which agents exist in the first place.

What do vendor registries add on top of the Agent Card?

A card describes one agent at one address. A registry adds a searchable inventory across many agents, with ownership and lifecycle data attached. Each vendor below covers a different part of that job.

These products are complementary layers. When you write requirements, decide which layer holds the authoritative record for each agent and which layers import from it. The cross-cloud guide covers how the layers connect.

How does the MCP Registry fit in?

The MCP Registry catalogs MCP servers. Its README says it provides MCP clients with a list of MCP servers, like an app store for MCP servers. The same README calls it a preview release in which breaking changes or data resets may occur.

Internal servers need somewhere else to live. The project states that the MCP Registry does not support private servers, meaning servers accessible only to a narrow set of users. For those, it recommends that you host your own private MCP registry.

Enterprise catalogs can carry public and internal entries side by side. Next to your own assets, MuleSoft's catalog includes a curated set of public MCP servers from the Official MCP Registry and Informatica.

What should a registry record hold?

Start from the Agent Card and add the fields an operator needs to run the agent. The vendor pages point to five groups.

  1. Identity and endpoint. Google's manual registration creates a Service resource that stores the agent's metadata, including its endpoint URL and configuration. Agent IDs there must be 4 to 63 characters and can contain only lowercase letters, numbers and hyphens.
  2. Protocol type. Google records A2A agents with the A2A_AGENT_CARD type and records agents that don't implement A2A using the NO_SPEC type.
  3. Capabilities and skills. Google's registry scans their agent-card.json Agent Card endpoint to index A2A skills. Capability flags in the card have consequences: a client that tries push notifications gets PushNotificationNotSupportedError when AgentCard.capabilities.pushNotifications is false.
  4. Governance metadata. Kong's registry lets you register ownership, versions, approval status, risk, authentication, policies, access and other metadata.
  5. Health. MuleSoft lets you see conformance status and instance health before you use an asset.

Treat what a card advertises as a claim. Microsoft tells Foundry users to carefully review and track the A2A agent endpoints they add. It also says that it didn't test or verify these A2A agent endpoints when third parties create them.

Who should own the registry and its entries?

Ownership should be split. A platform team owns the registry service, its access policy and its audit trail. The team that built each agent owns that agent's record and answers for its accuracy.

Access roles can enforce the split. In Google's registry, the role for writing entries is listed as Agent Registry API Editor. Microsoft Entra Agent ID separates technical administration from business accountability. Owners serve as technical administrators for agents, while sponsors provide business accountability without technical administrative access. The identity and access guide covers how to model both roles.

Decide which fields the registry verifies and which it only stores. The MCP Registry verifies publishers, who must verify ownership of their namespace through GitHub, DNS or HTTP challenges. Consumers may also ignore some card fields. Gemini Enterprise doesn't use the securitySchemes and security fields of an agent card to authenticate with the agent.

How do registries stay current as agents change?

Automate registration wherever a platform supports it, and assign a human reviewer to every entry it cannot cover. On Google Cloud, supported Google Cloud runtimes register your agents automatically. With a management boundary configured, Agent Registry automatically aggregates supported agents from member projects. Without one, automatic registration only discovers resources in the governance project, and remote agents need manual entries.

MuleSoft's Agent Fabric documentation describes scanners for this. They watch supported platforms and automatically register the agents, APIs and MCP servers they discover, and they can run on a schedule or on demand. Your requirements should ask how each product handles entries for agents that have been retired, and how it imports from each cloud you run. The RFP checklist has matching questions.

What do enterprise buyers ask?

Can a registry hold agents that do not speak A2A?

Some registries can. Google lets you register standard REST agents, which use the NO_SPEC type. MuleSoft describes an A2A bridge that presents those agents as A2A-compliant when they are not compliant by themselves.

Should host applications query the MCP Registry directly?

The MCP Registry project steers host applications away from reading it directly. It says the MCP Registry is not intended for direct consumption by host applications. Hosts should instead use a REST API conforming to the official MCP Registry OpenAPI spec, offered by other registries such as downstream marketplaces.

Which A2A version does Gemini Enterprise registration expect?

The A2A registration page says Gemini Enterprise supports the A2A v0.3 streaming mechanism. Agents on v1.0.0 or later should use the compatibility packages provided by the SDK so that they work with that earlier mechanism.

Which sources does this page cite?

Reviewed Nov 2026