Descovo — B2B contact data

com.descovoPublished by descovo.comOfficial publisherv1.0.0Updated Oct 29, 2026

B2B contact data for AI agents: search 700M+ people, reveal work emails. Pay per record.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Descovo's B2B contact data API, letting assistants discover and run operations to search 700M+ people and reveal work emails.

What you can do
  • Discover and rank Descovo API operations by intent, with optional constraints and tag filters
  • Browse curated tag packs and list all available endpoints with tag or search filtering
  • Read the complete schema and required fields for a specific operation before calling it
  • Execute any Descovo API operation by operation ID, such as company search, people search and contact enrichment
When to use it
Useful when an assistant needs B2B prospecting data — finding companies or people by role, location or industry, or revealing work emails for known profiles — and you want the assistant to pick and call the right Descovo endpoint itself.
Requirements
A remote endpoint at mcp.descovo.com over streamable HTTP. A Descovo API key is required, sent in the x-api-key header; a free account includes 500 credits. No local runtime or packages.
Before you install
Calls consume paid credits — the description says pay per record, so enrichment and search operations can cost money. The x-api-key header is a secret and is forwarded from the client config. Operations execute against a live third-party data service and may return personal contact data, so check consent and privacy obligations.

Installation

In SourceWeft

  1. Open Descovo — B2B contact data in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.descovo%2Fdescovo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "descovo-b2b-contact-data": {
      "type": "http",
      "url": "https://mcp.descovo.com/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

5

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.

ParameterslimitqueryrequiredtagPackconstraintsexcludedTagspreferredTags

list_tag_packs

List curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment).

Takes no parameters.

list_all_endpoints

List available Descovo API endpoints with optional tag/search filtering.

ParameterstagslimitsearchtagPack

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 schema, response schema, and example usage.

ParametersoperationIdrequired

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(operationId='...') first for complex/nested parameter shapes. Args: operationId: The operation ID to call params: Parameters dict: {"body": {...}, "path": {...}, "query": {...}} Returns: API response data or error details.

ParametersparamsoperationIdrequired

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.