Reading Time: 8 minutes

Agent Registry already routes every agent-to-server call through the Omni Gateway, and that’s where governance happens, including auth, schema checks, rate limits, PII masking. We previously brought hundreds of public MCP servers to Agent Registry. Now we’re expanding that catalog further with three servers from Informatica: Customer Identification, Data Provisioning, and Job Management.

The three Informatica servers

Why governance doesn’t need extra setup

In Agent Fabric, agents don’t call MCP servers directly — every call routes through the Omni Gateway first. A new server still needs its own credentials and entitlement to connect – but the governance is already there. A platform team sets policy once at the gateway, and it applies to every server from then on, without anyone touching the agent code.

Take the SSN case: the developer building the agent doesn’t write a masking rule. They don’t even need to know the field exists. The gateway detects it and strips it from the response before it reaches the model., because that policy was already in place.

What’s true of every release, including this one

  • New servers can easily plug into Omni Gateway. No separate governance setup required.
  • Every listing has the necessary metadata (what it does, why you’d use it, who built it), so you can tell if it fits before wiring it into an agent.
  • Once it’s in the registry, any team can reuse it through the same gateway and the same policies — no rebuilding the integration per project.

Availability: All three Informatica servers are live now in Anypoint Exchange.

What you need: Your existing Informatica credentials, plus the right entitlement — IDMC Master Data Management (MDM SaaS / Customer 360) for Customer Identification, Cloud Data Marketplace (CDMP) for Data Provisioning, and IDMC Cloud Data Integration for Job Management. You’ll also need Omni Gateway to actually enforce policy on the traffic.

The rest of the batch covers software delivery — code search (Sourcegraph), API test generation (Keploy), test insight (Cypress Cloud), mobile CI/CD (Appcircle), developer portals (Port), and deployment (Deployment.io, Sevalla) — along with security (Bright Security, Helixar, CodeRifts API Governance), notifications (Courier), media (Transloadit), localization (Tolgee, i18n Agent), commerce (Easyship), market data (Pyth Network, SEC EDGAR, Wokelo), and documents (Zoom Docs). These are all remote — nothing to install locally.

Example: How a meeting note becomes a governed action

Let’s say a team runs a weekly customer review over Zoom. The notes mention a customer by name and list a few follow-ups.

Normally, someone has to type all of that into a CRM, a ticketing tool, and maybe an email — sometimes copying the customer’s SSN along the way, with no real record of who touched it.

With Agent Registry, one agent can do this instead:

  1. Read the meeting notes through Zoom Docs and pull out the action items and the customer mentioned.
  2. Look up that customer through Customer Identification — fuzzy match finds the right record, then pulls it.
  3. As the record crosses Omni Gateway, the SSN in it gets masked automatically, before the agent’s model ever reads it.
  4. Route each action item to the right team via Courier, then write a summary back to Zoom Docs.

Nothing here required a new governance decision — it’s the same masking policy and the same gateway doing what they already do, just applied to a new server.

Ready to put this to work? Head to Agent Registry to browse the new Informatica servers, wire one into an agent, and see the Omni Gateway policies do their job on the first call. If you’re new to Public MCP servers, start with the Announcing the Availability of Public MCP Servers in Agent Registry then come back and add Informatica MDM to what your agents can already reach.

Additional resources: