com.descovo/descovo · v1.0.0 · sales-and-crm
Descovo — B2B contact data is healthy: it completed an MCP handshake in 436 ms and exposes 5 tools.
B2B contact data for AI agents: search 700M+ people, reveal work emails. Pay per record.
Endpoint: https://mcp.descovo.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 436 ms |
| Last checked (UTC) | 2026-10-30T01:05:22.457Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-30T01:05:22.457Z | Healthy | 436 |
search_endpoints | Canonical API selection tool for endpoint discovery and ranking. Use this first to get the top recommended operations for a user intent. Supports optional constraints plus tag-scoped selection via preferredTags, excludedTags, or a curated tagPack key. |
list_tag_packs | List curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment). |
list_all_endpoints | List available Descovo API endpoints with optional tag/search filtering. |
get_endpoint_details_full | Get COMPLETE schema and details for a specific API operation. Use this BEFORE calling an API to understand exactly what parameters are needed. Args: operationId: The operation ID (e.g., "syncContactEnrichment") Returns: Complete schema including all required/optional fields, request body |
call_operation | Execute any Descovo API operation by operationId. IMPORTANT: - apiKey is NOT required in the body if the MCP client sends an x-api-key header (most configs do). The backend auto-injects it. - Prefer search_endpoints() first when operation choice is ambiguous. - Use get_endpoint_details_full(operati |