Registry of registries

One catalog for every agent, MCP server and Skill. Wherever it was built.

Connect the registries you already run, or register directly. Every entry gets an owner. Nothing gets access just by being listed. What you approve reaches each employee in the AI assistants they already use.

Works with

Works with Microsoft Entra Agent ID, Google Agent Registry, GitHub, Official MCP Registry, SAP Agent Gateway, Copilot Studio, AWS Agent Registry, Gemini Enterprise, Microsoft Foundry, A2A Agent Cards, GitHub Enterprise Server, Private MCP registries, AI Catalog, Amazon Bedrock AgentCore.

Agents will come from everywhere.

Copilot agents live in Microsoft's registry. Gemini agents live in Google's. Skills sit in Git, with a copy in every AI assistant. MCP servers, the connections that let AI use your business systems, come from your API gateways and from public and private registries.

Each platform keeps its own list. Each has its own idea of what an agent is, its own rules and its own log. Nobody sees the whole picture, and every new platform adds one more list.

Five questions no single registry answers for the others.

  1. 1What do we have?
  2. 2Who owns it?
  3. 3Who may use it, and what may it do?
  4. 4What did it do?
  5. 5What does it cost?

Every platform answers for itself. Palma answers across all of them.

One catalog, fed from everywhere.

01

Connect.

Point Palma at the registries you already run: Microsoft, Google, GitHub and your MCP registries. Palma only reads them and keeps the catalog current on its own. Anything that has no registry, you register directly.

02

Own.

Every entry lands with a named owner, the team that owns the connection. Every agent also gets a human sponsor. No owner, no access. When people change teams, ownership can be handed over.

03

Decide.

Nothing in the catalog can be used until someone approves it. Approved capabilities go to the teams that need them, for example a "Finance close" bundle for the accounts team. Your identity groups decide who gets what.

04

Deliver.

People get what they're entitled to through one connector, in the AI assistants they already use: Claude, ChatGPT, Copilot Studio, Gemini, Cursor and 13 more. Every call through Palma is checked and recorded with three names: the human, the agent and the app.

Registries list.
Palma decides.

A registry tells you what exists. That is where most of them stop.

  • Discovered means nothing yet.

    New entries arrive with zero access. MCP servers wait to be adopted, and agents can wait for review.

  • Checked before anyone is served.

    Every Skill version is scanned. A flagged version is held back, and the last clean one keeps running.

  • Safe when a source changes.

    If an endpoint moves, nothing follows it without the owner's yes. If a registry suddenly returns nothing, Palma treats it as an outage, not as "delete everything".

  • Found, not registered.

    Agents that try to connect without being registered are listed, ready to be brought in.

Why a registry of registries, not one more registry.

  • All three kinds.

    Agents, MCP servers and Skills in one catalog. Vendor registries cover their own agents. Private MCP registries cover servers.

  • Nothing moves.

    Palma reads your registries and never writes to them. If you'd rather have one catalog only, register directly in Palma.

  • No platform to favour.

    Palma builds no agents and sells no AI assistant. Your rules don't depend on any one vendor's roadmap.

  • Per person.

    Your Entra or Okta groups decide what each person's AI gets, in every assistant they use.

  • Down to the action.

    Rules check what an agent is about to do: which amount, which recipient, which record. Risky steps wait for a person to approve them.

  • Sovereign.

    Hosted in Frankfurt, or self-hosted in your own cloud or data centre.

Keep what you've built.

  • Microsoft Agent 365 and Entra.

    Keep governing Microsoft agents there. Your Copilot Studio agents appear in Palma with their Entra identity, owner and sponsor, next to everything Microsoft doesn't hold.

  • Google Gemini Enterprise.

    Agents from Google Agent Registry join the same catalog, with the same owners and rules.

  • Your API gateways.

    The MCP servers you expose through them join the catalog with an owner. Your gateways stay where they are.

  • Your own registry.

    If it lives in Git or speaks the MCP registry API, point Palma at it.

Your AI register, where the agents are governed.

Every agent carries its model and version, use case, DPIA status and AI Act risk class. Protected fields can only be changed by named roles, and you can require a field before an agent goes live. Search the register by team, owner, status or your own fields, and export it for your auditor as CSV, JSON or Excel.

No more spreadsheet that goes stale the day after the audit.

Start with visibility.
Change nothing.

  1. 01

    Connect.

    Read-only. Nothing changes for any user.

  2. 02

    See.

    One catalog, owners assigned, unregistered agents found.

  3. 03

    Decide.

    Approve what should reach people, and bundle it per team.

  4. 04

    Control and count.

    Rules, human approvals and audit on top, plus AI spend per team and agent (in pilot).

FAQ

Questions about the registry of registries.

Do we have to move our agents or registries?

No. Palma only reads them. They stay where they are and keep their own names and descriptions.

Does connecting a registry give anything access?

No. Entries arrive with zero access. Each one needs an owner and an approval first.

We're standardising on Agent 365. Why Palma?

Keep Agent 365 for Microsoft agents. Palma reads your Entra agents and adds what sits outside Microsoft: your Skills, your MCP servers and the AI assistants your teams use beyond Copilot. It also decides what each person's AI may use and do in all of them.

We want one mandatory catalog, not a web of registries.

So do we. Register directly in Palma, with an owner and an approval on every entry. Connect a vendor registry only where agents are born there, such as Copilot Studio or Gemini Enterprise. It is still one catalog.

We built our own Skill or MCP registry.

Point Palma at it. Git repositories and registries that speak the MCP registry API connect directly.

Can we add our own fields?

Yes: use case, phase, GDPR and DPIA status, AI Act risk class and owners, with an EU preset. A field can be required before go-live.

Which standards do you read?

The official MCP registry API, GitHub, Microsoft Entra Agent ID, Google Agent Registry, AWS Agent Registry, A2A Agent Cards and the ARD and AI Catalog formats.

Does Palma write back to our registries?

No. Palma only reads.

Is this a gateway?

The catalog decides what exists, who owns it and who may use it. The connector applies those decisions on every call. Your API gateways stay as they are.

Where does it run?

In Frankfurt, or self-hosted in your own cloud or data centre.

See every agent, MCP server and Skill you have. Before anything changes.

Latest Blog Posts

Stay up-to-date with the latest in enterprise AI, MCP servers, and secure integration strategies.