{
  "id": "01-dropcontact",
  "slug": "dropcontact",
  "normalized_name": "dropcontact",
  "name": "Dropcontact",
  "vendor_url": "dropcontact.com",
  "category": "data-enrichment",
  "what_it_does": "A France-based, GDPR-oriented contact enrichment and email-finding/verification service that takes a name plus company (name, domain, or LinkedIn URL) and returns a verified professional email plus cleaned company data, with batch processing of up to 250 contacts at once.",
  "ai_features": "No strong AI claims found; the vendor's own positioning centers on \"triple verification\" and data-matching/deduplication logic rather than AI/ML. Treat as automation and rules-based verification, not AI-branded.",
  "mcp_status": "official",
  "mcp_url": "https://mcp.dropcontact.com/mcp ; https://www.dropcontact.com/mcp-dropcontact",
  "mcp_auth": "Hosted server at mcp.dropcontact.com/mcp/, supporting OAuth (recommended, browser-based) or a Dropcontact API token/key passed via headers; also usable through the npx mcp-remote bridge for clients without native remote-MCP support",
  "api_gate": "paid",
  "revops_role": "GDPR-conscious contact enrichment/verification layer for CRM hygiene and list-building; also a widely-used Clay waterfall step (Clay-managed account billed at 2 credits/enriched cell, with a 24h auto-update toggle).",
  "tier": "RESEARCHED",
  "last_checked": "2026-09-07",
  "sources": "https://www.dropcontact.com/mcp-dropcontact, https://developer.dropcontact.com, https://www.dropcontact.com/pricing, https://www.clay.com/integrations/data-provider/dropcontact, https://university.clay.com/docs/dropcontact-integration-overview, https://www.dropcontact.com/help/clay-integration, https://support.dropcontact.com/article/237-how-to-use-the-dropcontact-api-key, https://developer.dropcontact.com/, https://mcp.dropcontact.com/mcp",
  "notes": "Dropcontact is a clear \"official, vendor-built\" MCP - it has its own product page and a centrally hosted MCP endpoint at mcp.dropcontact.com, distinct from (and in addition to) its long-standing Clay data-provider integration. API & MCP access is bundled starting at the Starter tier (EUR 79/mo, ~500 credits/mo) and up; there is no persistent free API tier, only a \"50 free emails\" signup incentive. Pricing model is pay-on-success (1 credit = 1 email found or verified; credit refunded if nothing found). Lower tiers reportedly throttle API requests to ~100/min, which can bottleneck heavy Clay/n8n automation. 2026-09-03: vendor docs state the enrich endpoint (POST /v1/enrich/all) accepts \"first_name + last_name + company (or full_name + company)\" and its response includes a linkedin field with a linkedin.com/in/ example (https://developer.dropcontact.com/); no MCP tool name is stated there; the docs state a credit is charged only if a verified email is returned. 2026-09-07: https://mcp.dropcontact.com/mcp returned 401 with {\"error\": \"invalid_token\", \"error_description\": \"Authentication failed. The provided bearer token is invalid...\"} to an MCP initialize POST (https://mcp.dropcontact.com/mcp).",
  "mcp_status_bucket": "official",
  "api_gate_bucket": "paid",
  "mcp_urls": [
    "https://mcp.dropcontact.com/mcp",
    "https://www.dropcontact.com/mcp-dropcontact"
  ],
  "source_urls": [
    "https://www.dropcontact.com/mcp-dropcontact",
    "https://developer.dropcontact.com",
    "https://www.dropcontact.com/pricing",
    "https://www.clay.com/integrations/data-provider/dropcontact",
    "https://university.clay.com/docs/dropcontact-integration-overview",
    "https://www.dropcontact.com/help/clay-integration",
    "https://support.dropcontact.com/article/237-how-to-use-the-dropcontact-api-key",
    "https://developer.dropcontact.com/",
    "https://mcp.dropcontact.com/mcp"
  ],
  "source_annotations": [],
  "vendor_domain": "dropcontact.com",
  "display_name": "Dropcontact",
  "docs_url": null,
  "jobs": [
    "enrich-person-from-linkedin-url",
    "enrich-company-from-domain",
    "find-linkedin-url-from-name-and-company",
    "find-work-email",
    "verify-email-deliverable"
  ],
  "jobs_tagged_by": "machine-pass",
  "jobs_tagged_on": "2026-08-25",
  "github_url": null,
  "github_stars": null,
  "github_last_commit": null,
  "github_archived": null,
  "github_fetched_on": null,
  "github_candidates": [],
  "docs_digest": null,
  "docs_last_crawled": null,
  "submission": null,
  "mcp_tools": [],
  "mcp_tool_count": 0,
  "mcp_tools_evidence": null,
  "mcp_tools_repo": null,
  "mcp_tools_repo_party": null,
  "mcp_catalog_shape": null,
  "mcp_catalog_note": null,
  "mcp_tools_fetched_on": null,
  "cli_status": "none-found",
  "cli_party": null,
  "cli_binary": null,
  "cli_install": [],
  "cli_login": null,
  "cli_commands_seen": [],
  "cli_docs_url": null,
  "cli_repo": null,
  "cli_packages": [],
  "cli_evidence": null,
  "cli_checked_on": "2026-09-27",
  "github_org": null,
  "github_org_status": "unresolved",
  "github_org_url": null,
  "github_org_evidence": {
    "rule": null,
    "reason": "github candidates were seen but none passed the evidence rules",
    "candidates_rejected": [
      {
        "login": "dropcontact-d",
        "from": "rule 3 (Dropcontact)",
        "type": "Organization",
        "website": null,
        "rejected": "website (none) does not match dropcontact.com"
      }
    ]
  },
  "github_org_repos": 0,
  "github_org_repos_mcp": 0,
  "github_org_repos_cli": 0,
  "github_org_latest_activity": null,
  "github_org_recent_repos": [],
  "github_org_checked_on": "2026-09-08",
  "mcp_endpoint": null,
  "mcp_docs_url": "https://www.dropcontact.com/mcp-dropcontact",
  "endpoint_status": "docs-only",
  "endpoint_http_status": 200,
  "endpoint_last_probed": "2026-09-04",
  "endpoint_wall_note": null,
  "canonical": true,
  "canonical_id": "01-dropcontact",
  "also_listed_in": [],
  "source_file": "01-data-enrichment.md",
  "source_line": 257,
  "file_index": 13,
  "category_num": "01",
  "category_slug": "data-enrichment",
  "category_label": "Data & Enrichment",
  "heading": "Dropcontact",
  "missing_schema_fields": [],
  "extra_fields": {},
  "display_rank": 86
}