Crustdata
by Crustdata
Search and enrich B2B company and people data from an AI agent. 23 credit-metered tools return named individuals with work history, personal emails and phone numbers. One tool creates a standing webhook that tracks a named person indefinitely.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Crustdata via MCP
https://mcp.crustdata.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Crustdata Tools & Capabilities (23)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The scope boundary sits in the right place, but nothing enforces which tools you granted. The server's RFC 9728 descriptor declares
scopes_supportedasreadandwrite, verified live on 2026-08-23 — a genuine two-value split, unlike the empty arrays and identity-only claims most connectors ship. It separates the 21 reads from the two watcher writes. It does not separate a company lookup from a personal-phone-number lookup, which is the boundary a privacy-conscious reader would actually want. We did not verify that the server enforces the scope it advertises. - Every people tool is a personal-data tool. There is no aggregate-only mode. If the risk you are managing is exposure of individuals' contact details to an agent, this connector cannot be configured to avoid it.
- Crustdata names none of its data sources. "15+ sources" is the entire published claim.
- No public data licence governs connector output. The public Terms page covers the website only. Your commercial agreement is the operative document and we have not seen it.
- A watcher outlives the conversation.
crustdata_watcher_createstarts a recurring job with no documented expiry by default, and no tool in the listing deletes one. - Costs are per result, not per call. A broad search bills for every record it returns, and the agent does not see the bill until after the call.
- Rate limits are per endpoint and low on the expensive ones. Crustdata documents 15 requests per minute on person enrich, 30 on person search, and 5 to 10 on the live and batch endpoints, returning HTTP 429 when exceeded. Limits vary by plan.
- Some fields need account-level permission. Crustdata's person enrich reference marks certifications, honors and the permanent URN-based profile URL as requiring field-level permission on the API key, so two accounts can get different results from the same call.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail on this page comes from the server itself.
- A second Crustdata MCP server exists and is a dispatcher. The vendor's own install links point at it. Nothing on this page describes its reachable surface.
- The support address differs between sources. Anthropic's directory and Crustdata's older MCP page give
support@crustdata.com; its newer pages givesupport@crustdata.co. Both appear in first-party material.
Frequently asked questions
Yes, directly and by design. Crustdata's own documentation describes 800 million professional profiles, and the person enrich response returns a basic_profile section carrying name, first name, last name, headline, current title, location and profile picture, plus full employment history and education. This is not an aggregate surface with a person-level dimension hidden inside it. Named individuals are the product.
Yes. Crustdata's contact enrichment documents three requestable contact types: business emails at 1 credit per matched person, personal emails at 2 credits, and phone numbers at 2 credits. The connector's people enrich tool reaches this surface. Crustdata's own MCP page lists the example prompt asking Claude to get the email for a person's profile.
Crustdata does not publish a source list. Its people dataset page claims 1 billion people from 15-plus sources with 95-plus datapoints per person, but never names those sources. The API is organised around professional network profile URLs as the primary identifier, and the docs describe real-time retrieval from the web. We could not establish whether any given record was scraped, licensed or contributed.
Crustdata publishes no data licence answering this. Its only public Terms page is website-materials boilerplate governing downloads from crustdata.com, granting a personal, non-commercial viewing licence to the website and saying nothing about API or connector output. The contract that actually governs your data use is your commercial agreement, which is not public. Ask before publishing connector output.
Most of them do. Crustdata prices per result and per record, not per call: person search at 0.03 credits per result, person enrich at 1 to 7 per record, company enrich at 2 to 4, web search and fetch at 1 each, and a person entity watcher at 5 to 150 credits per changed person. Identify and autocomplete are free.
Yes. The crustdata_credits_check tool is free and reads the account balance, the recurring grant and the next refresh date. Crustdata also returns an X-Credits-Used header on every API request. This is the accounting tool that many metered connectors omit, and it means an agent can be instructed to check the balance before a large batch.
It creates and updates watchers, and nothing else. Three of the 23 tools mutate state: crustdata_watcher_create, crustdata_watcher_update and, on the vendor's own reading, nothing destructive. No tool deletes a watcher. The RFC 9728 descriptor advertises a write scope, verified live on 2026-08-23, which matches these two names rather than pointing at a hidden surface.
It starts recurring surveillance of named people and pushes it to a URL you choose. Crustdata documents watcher notification channels as a webhook with an arbitrary url and arbitrary headers, a Slack webhook, or Google Chat. A person entity watcher re-runs on a schedule, compares each watched person against their last snapshot, and delivers the changed profile fields outward.
Sources
- Crustdata MCP server documentation, the page Anthropic's directory nominates, including the 23-tool table and credit costs (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata documentation index — · full corpus at (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata newer MCP server page, describing the three-tool dispatcher at install.crustdata.com (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Pricing, per-endpoint credit costs and watcher freshness tiers (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Rate limits, per-endpoint RPM table (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Person Enrich reference, the person_data section catalog (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Person Contact Enrich, contact types and per-type credit costs (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Identify (Reverse Email Lookup) (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Person Search reference, filterable and sortable field table (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Person Entity Watcher, delivery channels and tracking behaviour (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Credits and Permissions endpoints — · (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata people dataset page, the 1 billion people and "15+ sources" claims (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Terms and Conditions (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata Privacy Policy, GDPR Article 21 objection and 30-day removal (retrieved 2026-08-23) · retrieved 2026-08-23
- Crustdata documentation
robots.txt, carryingContent-Signal: ai-train=yes, search=yes, ai-input=yes(retrieved 2026-08-23) · retrieved 2026-08-23 - Live auth posture check: anonymous
initializereturned 401 with awww-authenticatechallenge; RFC 9728 metadata athttps://mcp.crustdata.com/.well-known/oauth-protected-resource/mcpdeclaringscopes_supportedof read and write; authorization server metadata athttps://mcp.crustdata.com/.well-known/oauth-authorization-server(2026-08-23) · retrieved 2026-08-23 - Aura MCP server page, for the aggregate-boundary comparison (retrieved 2026-08-23) · retrieved 2026-08-23
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Crustdata support — <mailto:support@crustdata.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- Crustdata
- Tools
- 23
- Domain
- mcp.crustdata.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.