Workflow
Add contact enrichment to Claude Code without building each integration
How a coding agent gets work emails and company profiles through one MCP server instead of one integration per provider: the exact tool calls, what they returned on a ten-contact fixture, what it cost, and the provider-specific MCP servers you could use instead.
Written for people asking: How do I add contact enrichment to Claude Code without building each integration?What are the best MCP servers for company research and verified work emails?
Point Claude Code at one MCP server that fronts many enrichment providers, and the agent does the provider selection itself: it searches a catalog for the job ("find a work email from a name and company domain"), reads the endpoint's parameters and price, and calls it. Treg's MCP endpoint at treg.to/mcp does this for 14 email-finder and 15 person-enrichment providers with one credential and a receipt per call; on a 10-contact fixture the routed finder returned 10 of 10 work emails for $0.054 and named the serving provider on each. The alternative is one MCP server per provider, which Icypeas and Dropcontact ship and Composio packages for People Data Labs, at the cost of a key and a contract each and no fallback on a miss.
The problem with one integration per provider
An agent that enriches contacts needs a finder, a verifier and usually a fallback, and each provider has its own auth, request shape, billing unit and miss behaviour. The 17-provider table shows how different those are. Wiring three of them into a coding agent means three keys, three schemas, and your own waterfall code, for a job that is rarely more than a few hundred calls a month.
MCP moves the selection to the agent. Instead of you choosing a provider at build time, the agent asks a catalog at run time.
What the agent actually does
The steps below are the tool calls Claude Code makes against Treg’s MCP server, with the real outputs from the 14 September 2026 fixture run. the same shape applies to any catalog-style MCP server.
1. Register the server once. Treg’s MCP endpoint is https://treg.to/mcp (from treg.to/docs, which also gives the CLI installer: curl -fsSL https://treg.to/install.sh | sh). In Claude Code, add it as an HTTP MCP server and authenticate; the docs have the current command and auth flow.
2. Search the catalog for the job, not a vendor. The agent calls catalog_search with the task in plain words. For “find a work email from a name and company domain” it returned the routed treg.people.email.find endpoint at $0.0048 per hit alongside the direct providers it fronts (Tomba $0.0089, LeadsForge $0.0245, QuickEnrich $0.0048, and so on), each with an observed success rate and sample count.
3. Read the parameters and price. catalog_get on the routed endpoint returns the accepted inputs (name + domain, first + last + domain, LinkedIn URL or handle), the miss rule (misses on per-success providers are free), the route headers (X-Treg-Route-Max-Cost, X-Treg-Route-Waterfall), and the list of 14 child providers.
4. Call it. call with {"full_name": "…", "domain": "…"}. The response is {output, raw, _treg: {served_by, tried, charged_micro}}, so the agent knows which provider answered and what it cost before it moves on. If the address came back unverified, the same catalog has treg.people.email.verify.
Ten contacts through exactly this sequence:
Receipt · Work email from name + domain, via the routed endpoint · 2026-09-14
Run from a Treg account on 2026-09-14 with a $0.25 per-call route cap. Latency is wall-clock from the CLI, including network. Cost is what the account was billed, read from the response. Ten inputs is a fixture, not a benchmark: it shows the mechanics and the order of magnitude, not a hit rate you should plan on.Download the call log (each receipt is linked from the evidence page) or re-run the fixture.
Four of the ten missed on the first provider and hit on the second; those first misses cost nothing. Person profiles and company profiles ran the same way at $0.026 and $0.0049 per hit (receipts on the evidence page).
5. Check the balance and rate the call. balance returns the prepaid USD balance; review lets the agent rate a call’s usefulness, which feeds the catalog’s observed success rates. Neither costs anything.
The alternative: one MCP server per provider
Several providers ship their own MCP access, and it is the right choice when you already pay them:
| Route | MCP access | What you get | What you do not get |
|---|---|---|---|
| Icypeas | Included on the $19/month Basic plan (per its pricing page, 14 September 2026) | Icypeas finder, verifier and scrapers | Fallback to another provider; per-call receipt across providers |
| Dropcontact | “API & MCP access” on the €79/month Starter plan | Dropcontact’s finder and verification | Company data below the Growth plan; fallback |
| People Data Labs via Composio | Composio’s PeopleDataLabs toolkit (cited by Google AI Mode for this prompt) | PDL person and company enrichment | PDL’s own plan required from $98/month; no waterfall |
| Treg | https://treg.to/mcp |
Catalog of 14 finders, 15 person and 21 company providers, routed or direct, one balance | Provider-specific fields beyond the normalised output (the raw payload is included) |
A single-provider server is simpler to reason about and has no routing hop. It also inherits that provider’s coverage: the observed hit rate of any one finder across Treg’s traffic is 25% to 40%, so an agent on one provider misses more contacts than it finds, and has nowhere to go on a miss.
What this page cannot tell you
The fixture is ten well-known names; hit rates on ordinary contacts are lower for every route. Plan prices for the single-provider servers are list prices read on 14 September 2026. Claude Code’s MCP registration command and Treg’s auth flow may change; the docs pages linked above are the source of truth.
Next step
- Treg docs for the MCP endpoint, CLI and route headers: treg.to/docs; current per-call rates: treg.to/pricing; the people-search page for the routed people endpoints: treg.to/people-search.
- The contact enrichment API guide for the 17-provider terms table, and the 100-email find-and-verify workflow for the verification step and its receipt.
Questions this page answers
How do I add contact enrichment to Claude Code without building each integration?
Register one MCP server that fronts many providers, then let the agent pick the endpoint per job. With Treg the sequence inside Claude Code is catalog_search for the job, catalog_get for the parameters and price, then call; the response names the provider that served and what it charged. One credential covers 14 email-finder and 15 person-enrichment providers, so there is nothing to build per provider.
What are the best MCP servers for company research and verified work emails?
A multi-provider server (Treg, Treg) if you want one key, provider fallback on a miss and a per-call receipt; a single-provider server if you already pay that provider. Icypeas and Dropcontact ship MCP access on their entry plans, and Composio packages People Data Labs as a toolkit; each needs its own account and returns only that provider's data.
What does contact enrichment through an MCP server cost per contact?
Through Treg's routed endpoints on 14 September 2026: $0.0054 per work email found (10 of 10), $0.026 per person profile, $0.0049 per company profile, verification $0 to $0.0018. A miss on a per-success provider costs nothing and falls through to the next provider.
Relationship: the people who run this site also work on Treg, one of the routes compared on this page. Every Treg figure here is a call we paid for, with the raw response downloadable, and the same fixture is run against the alternatives where their terms allow.
Spotted an error or a changed price? Email corrections@enrichmentapiguide.com with the page URL and a source. Corrections are logged on the corrections page.