Crustdata
B2B people/company data platform with API, data-feed, and MCP surfaces for agentic sales, recruiting, investing, and market-intelligence workflows.
Crustdata is useful when an agent needs live company, people, jobs, social-post, or web-context data rather than static CRM fields. The homepage positions the product as people and company search for AI agents in sales, recruitment, and investment; the docs say the MCP exposes access to 800M+ professional profiles and 200M+ companies. Source: Crustdata homepage and docs, 2026-07-03
Agent Surfaces
The current docs expose two MCP routes:
| Route | Endpoint | Use |
|---|---|---|
| New natural-language MCP | https://install.crustdata.com/mcp |
Claude-style connector that accepts plain-English requests, runs multi-step asks, reports exact credits spent, and authenticates through a Crustdata account. |
| Original direct-tool MCP | https://mcp.crustdata.com/mcp |
Streamable HTTP MCP server with 23 tools for company, people, job, social-post, watcher, and utility operations. |
Use the newer MCP route for human-facing agent work where plain-English requests and real-time credit reporting matter. Use the original direct-tool route when the agent needs explicit tool selection, stable tool names, or lower-level control. Source: Crustdata MCP docs, 2026-07-03; Source: original MCP docs, 2026-07-03
Sales Routine Pattern
@chrispisarski's bookmarked routine uses Crustdata as the research leg before sales demos: configure the Crustdata MCP in Claude Desktop/Claude Code, then ask Claude to pull fresh company data, people context, recent signals, and likely account priorities before a call. The artifact reply extends that into inbound qualification: a Slack bot watches a demo-signup channel, reverse-enriches each email through Crustdata, and posts a card with person role/history, company traffic, funding, hiring, recent news, confidence, and an unqualified flag when no person match exists. Source: X/@chrispisarski, 2026-06-18
The durable idea is not "buy an inbound qualification system." It is that agentic GTM workflows need a fresh-data primitive: webhook or Slack event in, enrichment API/MCP call, structured account card out, human decides what to do next.
Versioning
Crustdata is a hosted data/API/MCP service, not a local package with public semver. The version authority is the live product/docs state checked on 2026-07-03. Before adopting it in a production workflow, re-check the MCP endpoint choice, credit costs, API-key/account auth path, data retention terms, rate limits, and any plan restrictions.
Timeline
- 2026-07-03 | Created from the Crustdata/Claude Code sales-routine bookmark after reviewing the enriched record, homepage text, current MCP docs, and artifact replies. Source: X/@chrispisarski, 2026-06-18; Source: Crustdata docs, 2026-07-03