The GTM MCP Directory
Directory / Data & Enrichment / UpLead

UpLead

Community MCP Paid, self-serve Data & Enrichment RESEARCHED Checked 2026-09-03
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: uplead.com · entry id 01-uplead · source 01-data-enrichment.md line 331

What it does
A B2B contact database and prospecting tool (vendor claims 160M+ contacts, 95% data accuracy) for building lead lists with verified emails, direct dials, and firmographic/technographic filters, with a browser extension and CRM integrations.
AI features, separated from automation with an AI label on it
No distinct AI/ML feature set found beyond standard match-and-verify logic (real-time email verification, intent-data overlays). Marketing emphasizes "accuracy" and "verified," not AI - functionally this is a traditional enrichment database rather than an AI product, despite appearing in "AI tools" roundups.
RevOps role
Prospecting/list-build and enrichment source; lower self-serve tiers cover manual search, CSV export, and a limited real-time Enrichment API, while full API/integration-building access requires the top custom-priced tier.
MCP server
Status bucket
Community MCP
Auth
Handled through the Zapier/Pipedream platform's own connector auth (API key entered into that third-party platform), not a UpLead-native OAuth or API-key flow
Parsed URLs
2 found in the mcp_url field
Endpoint probe
docs page, not an endpoint
Probed
2026-09-04, HTTP 200

A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established by hand on 2026-09-03. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.

mcp_status, verbatim from the file:

community

mcp_url, verbatim from the file:

https://zapier.com/mcp/uplead (also listed on Pipedream: https://mcp.pipedream.com/app/uplead)

What this server exposes

Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the tools index.

Command line

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

Access gate
Gate bucket
Paid, self-serve
Can a solo operator reach it
Yes, by paying, no sales call

api_gate, verbatim from the file:

paid

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

On GitHub

No GitHub organisation could be tied to uplead.com with evidence on 2026-09-08.

Recorded by the harvest: github candidates were seen but none passed the evidence rules.

4 candidate accounts seen and rejected by the evidence rules: uplead, UpLeady, uplead-me, Uplead-Digital. A name match alone is never accepted; the account has to point at the vendor domain.

Jobs it can do

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

Sources

6 source URLs. Raw sources field, verbatim:

https://www.uplead.com/pricing/, https://zapier.com/mcp/uplead, https://mcp.pipedream.com/app/uplead, https://www.landbase.com/blog/uplead-pricing, https://www.cleanlist.ai/blog/2026-07-15-uplead-pricing-guide, https://docs.uplead.com/

Notes, verbatim from the file
No dedicated UpLead-built MCP server was found on github.com, mcp.so, glama.ai, or pulsemcp.com - the only "MCP" listings are generic Zapier/Pipedream action-wrapper connectors, so this is marked community/third-party, not an official protocol-native server. Pricing: Essentials ($99/mo billed monthly, ~$74/mo annual) and Plus ($199/mo, ~$149/mo annual) are self-serve and include a limited real-time "Enrichment API" (Plus adds a "Prospector Pro API" for search). Full/unrestricted API access is reserved for the Professional tier - annual-only, custom-priced, "Book a Demo" only, no self-serve checkout - functionally enterprise-gated for complete API use. 2026-09-03: vendor docs state the Person API (https://api.uplead.com/v2/person-search) takes first_name, last_name and domain and returns linkedin_url (https://docs.uplead.com/); the only MCP surfaces are the Zapier and Pipedream community wrappers, which name no such tool; the docs state "One credit will be deducted for each contact or company record that you receive", charged only when the email status is Valid or Accept All.
Provenance
Entry id
01-uplead
Source file
01-data-enrichment.md
Source line
331
Tier
RESEARCHED
last_checked
2026-09-03
Data baked
2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.