The MCP server for B2B enrichment

"MCP server for B2B enrichment" is a search that barely existed a year ago. Now it's how agents find their tools. The Model Context Protocol lets an AI agent call an external capability — enrichment, here — as a native tool, without anyone writing an integration first. So the useful question isn't whether a server exists; it's which enrichment servers are worth connecting, and what separates a real one from a thin wrapper around a REST endpoint.

What makes an MCP enrichment server good (not just present)

Any REST API can be wrapped in an MCP shim. The ones worth an agent's trust do four things the shim doesn't:

• Real tool semantics. Typed inputs, clear tool names, and annotations that mark each tool read-only or destructive — so the agent knows what's safe to call without asking.
• Attributed results. Every field returned with its source and a confidence score. An agent can act on a cited value; it has to guess about a bare one.
• OAuth, not a key pasted into the prompt. The connector owns authentication. Keys in prompts are a leak waiting to happen.
• One call, many sources. The server resolves the providers behind a single request. Orchestrating ten APIs is the agent's job you're trying to remove, not add.

The servers worth connecting

abm.dev

The account-based marketing API for AI agents, MCP-native at https://mcp.abm.dev/mcp. OAuth 2.1, typed tools for search, source, enrich, and create, and every enriched field returned with its source and a confidence score — cited, or not returned. One key, one schema, ten sources resolved behind a single call.

Explorium and others

Explorium markets an MCP-native enrichment surface with broad coverage; a handful of others are appearing. The registries — mcp.so, the official MCP registry, Glama — are where to browse them. Apply the four tests above to any of them; most REST wrappers fail on attribution.

How to connect abm.dev

In Claude, add https://mcp.abm.dev/mcp as a custom connector and complete the one-time OAuth sign-in. For clients that want a local command, npx @abmdev/mcp runs a thin bridge to the same hosted server. Either way the agent gets the same typed tools.

The test

Connect it, then ask the agent to enrich a person from an email. Watch what comes back: not a wall of fields, but the ones the server can stand behind, each with its source. That's the difference between an enrichment server built for agents and a REST API wearing an MCP badge.