CrustData Screener MCP Server
Connect Claude Desktop to CrustData's B2B data platform. Search companies, enrich data, and find decision makers directly from Claude.
Installation
pip install crustdata-screener-mcp
Setup
1. Get your CrustData API token
- Sign up at crustdata.com
- Get your API token from your dashboard
2. Configure Claude Desktop
Add to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"crustdata": {
"command": "crustdata-mcp",
"env": {
"CRUSTDATA_API_TOKEN": "your_api_token_here"
}
}
}
}
3. Restart Claude Desktop
That's it! The CrustData tools are now available in Claude.
For Claude CLI Users
If you're using Claude CLI instead of Claude Desktop:
claude mcp add crustdata "crustdata-mcp" \
-e "CRUSTDATA_API_TOKEN=your_api_token_here"
# Verify connection
claude mcp list
Usage Examples
Ask Claude:
- "Search for AI companies with 50-200 employees"
- "Get information about Stripe including funding and headcount"
- "Find the LinkedIn profile of John Doe at Apple"
- "Search for recent LinkedIn posts about product launches"
Available Tools
-
Company Search & Enrichment
search_companies- Search with filtersenrich_company_data- Get detailed company infoidentify_company- Find companies by name/domain
-
People Search & Enrichment
search_people- Find people by title, company, locationenrich_person_profile- Get detailed person info
-
LinkedIn Data
get_linkedin_posts- Retrieve LinkedIn postssearch_linkedin_posts_by_keyword- Search posts by keywords
Environment Variables
CRUSTDATA_API_TOKEN(required) - Your CrustData API tokenCRUSTDATA_API_BASE_URL(optional) - API base URL (defaults to production)
Support
- Documentation: docs.crustdata.com
- Issues: github.com/crustdata/mcp-server/issues
- Email: support@crustdata.com
License
MIT
Metadata
Release files for crustdata-screener-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| crustdata_screener_mcp-1.0.3.tar.gz | 15.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| crustdata_screener_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.7 kB
Release files / crustdata_screener_mcp-1.0.3.tar.gz
| Download URL | crustdata_screener_mcp-1.0.3.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf73ef22e482264b9f9fa534bae7efa988dc57c14c256c56ab332a6d279b82f4
|
|
BLAKE2b-256 checksum How to use checksums |
21d286281448d9e8270af9e3067ccf3136c128d1dda22f0cc9942db929e07570
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.16
|
Release files / crustdata_screener_mcp-1.0.3-py3-none-any.whl
| Download URL | crustdata_screener_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27bd59d554d45f343e21042e1c5c233d01d9ef8a5702bb9fb0fb528e0975bb28
|
|
BLAKE2b-256 checksum How to use checksums |
64f7066b7f9e43452c8bad69d65e1aad1a11a255e79f8d5cab448bc5f8a4139b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.16
|
Security for crustdata-screener-mcp 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.