OpenLeads
PYPI · OPENLEADS
Find leads with honest email evidence, then work them: CRM, sequences, tasks, deals. No API keys.
Available components
Last scanned (19 hours ago)
Scores higher than 66% of PyPI servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1443 tokens (~65/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 −17
- Malware scan: pass → unverified ▼ security
- Tool coverage: 57% → 33% ▼ functional
- Schema quality: 284 → 1443 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → fair functional
- Package version: 4.6.1 → 5.0.0 functional
- 14 Oct 26 +27
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 57 functional
- First check of Schema quality: good functional
- 13 Oct 26 40
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed pypi/openleads@5.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_note ~46
Add a note to a contact's record (call notes, context, next steps).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| pinned | boolean | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
add_to_list ~39
Add saved contacts to a people list (created if it doesn't exist).
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Contact emails. |
| list | string | yes | – |
No output schema declared.
No examples provided.
complete_task ~31
Mark a task done (a sequence task moves that contact to their next step).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
create_deal ~87
Open a deal. stage: qualify, meeting, proposal, negotiation, won, lost. amount accepts 12000, 12k or $2.5k.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| close_date | string | – | – |
| company | string | – | Domain. |
| contact | string | – | – |
| name | string | yes | – |
| stage | string | – | – |
No output schema declared.
No examples provided.
create_task ~92
Create a follow-up task. kind: call, email, linkedin or todo. due accepts today, tomorrow, +3d, +2h, a weekday (fri) or YYYY-MM-DD.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Contact email. |
| due | string | – | – |
| kind | string | – | – |
| note | string | – | – |
| priority | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
enroll_in_sequence ~80
Add contacts (by email or a whole list) to an existing sequence. People who are suppressed, unverified, or already in a sequence are skipped with a reason. Nothing is sent immediately; steps run on schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | – | Contact emails. |
| list | string | – | – |
| sequence | string | yes | Sequence name or id. |
No output schema declared.
No examples provided.
find_email ~57
Find the most likely work email for a person at a company domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain, e.g. 'acme.com'. |
| name | string | yes | Full name, e.g. 'Ada Lovelace'. |
No output schema declared.
No examples provided.
find_leads ~161
Find B2B leads from free public sources and verify their emails. Describe who you want in plain English, e.g. 'dentists in Austin', 'marketing agencies in Miami', 'fintech founders', 'rust developers in Berlin', or 'emails at stripe.com'. Returns people/companies with an email, a deliverability tier (safe/risky), and evidence (found/pattern/guessed).
| Name | Type | Req | Description |
|---|---|---|---|
| budget_seconds | integer | – | – |
| count | integer | – | – |
| query | string | yes | Who to find, in plain English. |
| save_to_list | string | – | Also save the results to your workspace, in this list (created if new). |
| verified_only | boolean | – | Only return deliverable (safe-tier) emails. |
No output schema declared.
No examples provided.
get_company ~33
One company: profile, tech stack, its people, deals, open tasks and notes.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_contact ~43
Everything about one contact: profile, company, tags, lists, notes, open tasks, deals, sequences they're in, and recent activity.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
No output schema declared.
No examples provided.
list_sequences ~21
Outreach sequences with their steps, status and reply/bounce numbers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sources ~19
List the public data sources OpenLeads can search.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tasks ~36
The follow-up queue (calls, emails, LinkedIn touches, to-dos) by due date.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | – |
No output schema declared.
No examples provided.
move_deal ~38
Move a deal to another stage (won makes its contact and company customers).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| stage | string | yes | – |
No output schema declared.
No examples provided.
pipeline ~29
The deal pipeline by stage with totals: open value, probability-weighted forecast, won value and win rate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
save_contacts ~81
Save people to the workspace (e.g. results from find_leads), optionally into a list and with tags. Existing contacts are updated without blanking fields. Each contact needs an email; other fields are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | – |
| list | string | – | Add them to this list (created if new). |
| tags | array | – | – |
No output schema declared.
No examples provided.
search_companies ~75
Search companies in the workspace by text, technology they use (e.g. HubSpot, Shopify), industry or stage. Returns people counts and tech stack.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | – |
| limit | integer | – | – |
| query | string | – | – |
| stage | string | – | – |
| technology | string | – | – |
No output schema declared.
No examples provided.
search_contacts ~222
Search the people saved in your OpenLeads workspace (like Apollo's People tab). Filter by free text (name, email, company, title), stage, email status, seniority, department, tag, list, or minimum ICP fit score. Returns contacts with stage, fit score (0-100) and email tier.
| Name | Type | Req | Description |
|---|---|---|---|
| department | string | – | e.g. sales, marketing, engineering, executive |
| fit_min | integer | – | – |
| limit | integer | – | – |
| list | string | – | List name. |
| never_contacted | boolean | – | – |
| query | string | – | Words to match in name, email, company or title. |
| seniority | string | – | owner, founder, c_suite, partner, vp, head, director, manager, senior, entry |
| stage | string | – | new, approaching, replied, interested, meeting, customer, not_interested, unresponsive, do_not_contact, bad_data |
| tag | string | – | – |
| tier | string | – | Email status: safe or risky. |
No output schema declared.
No examples provided.
set_stage ~56
Move contacts to a stage: new, approaching, replied, interested, meeting, customer, not_interested, unresponsive, do_not_contact, bad_data.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Contact emails. |
| stage | string | yes | – |
No output schema declared.
No examples provided.
tag_contacts ~44
Add (or with remove=true, remove) tags on contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Contact emails. |
| remove | boolean | – | – |
| tags | array | yes | – |
No output schema declared.
No examples provided.
verify_email ~33
Check whether an email address is deliverable (safe/risky/bad) and why.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
No output schema declared.
No examples provided.
workspace_stats ~33
The workspace at a glance: contacts, sends, reply rate, tasks due, pipeline, ICP grades and data-quality issues.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the OpenLeads MCP server?
OpenLeads runs locally as a PyPI package, launched with uvx openleads. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · openleads
claude mcp add samyrrrrrr990-openleads -- uvx openleads
What is the OpenLeads MCP server?
OpenLeads is an MCP server listed in the public MCP registry as io.github.Samyrrrrrr990/openleads. Find leads with honest email evidence, then work them: CRM, sequences, tasks, deals. No API keys. This page covers its PyPI package (openleads).
Is the OpenLeads MCP server safe to use?
OpenLeads scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OpenLeads MCP server expose?
OpenLeads exposes 22 tools: find_leads, find_email, verify_email, list_sources, search_contacts, and 17 more. Their descriptions and schemas cost roughly 1,356 tokens of context every time the server is loaded.
Is the OpenLeads MCP server still maintained?
OpenLeads is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the OpenLeads MCP server under?
OpenLeads declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.