ai.lakewave/lakewave-mcp
PYPI · LAKEWAVE-MCP
Verified B2B contacts at named accounts, email verdicts, contract signals and drafted campaigns.
Available components
Last scanned (2 hours ago)
Scores higher than 45% 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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 975 tokens (~88/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 5 Nov 2026 · Analysed pypi/lakewave-mcp@1.0.1
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 | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
account ~21
Plan, remaining credits, prices and request limits for this API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contracts_ending ~143
Public-sector (state, county, city, K-12, higher-ed) contracts ending inside the window: agency, incumbent vendor, title, end date, amount and source link. states: comma-separated two-letter codes ("CA,TX"); terms: free text matched against title, agency, vendor and vehicle. These are purchases an agency has to re-buy, i.e. rebid and competitive-takeout targets. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| months | integer | – | – |
| page | integer | – | – |
| states | string | – | – |
| statewide_only | boolean | – | – |
| tech_only | boolean | – | – |
| terms | string | – | – |
No output schema declared.
No examples provided.
create_campaign ~125
Create a Lakewave campaign with a target set of companies. With draft=true and titles given, Lakewave finds the best person at each company and writes a personalized draft for each (4 credits per verified person plus 1 per draft). Drafts wait in the Lakewave app for a human to approve and schedule; this tool never sends email. Returns the campaign id and the app link.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| draft | boolean | – | – |
| location | string | – | – |
| name | string | yes | – |
| titles | array | – | – |
No output schema declared.
No examples provided.
email_format ~99
A company's email convention. 'confirmed' means Lakewave has verified real addresses at that domain in that shape; 'evidence' means seen publicly; 'guess' means nothing on record yet. With first and last, returns rendered candidate addresses labelled by basis. Free. Candidates are not verified until you run verify_emails on them.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| first | string | – | – |
| last | string | – | – |
No output schema declared.
No examples provided.
find_people ~180
Find and verify the people in the given roles at the given companies. companies: 1-25 company names. titles: 1-5 role titles (e.g. "Director of IT"). location: optional territory ("Texas", "Bay Area"); location_mode "hq" keeps companies headquartered there, "people" keeps people located there. Returns only people at Lakewave's 4-star verified bar: name, title, company, email, stars, LinkedIn. Costs 4 credits per verified person; a search that finds nobody costs nothing. Waits up to wait_seconds; if still running, returns the job_id to resume with get_job.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| location | string | – | – |
| location_mode | string | – | – |
| titles | array | yes | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
get_campaign ~33
Campaign rollup: company statuses, draft / approved / sent counts, drafting progress.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
No output schema declared.
No examples provided.
get_job ~34
Status and results of a find_people job. People are included once the job is done.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_list ~25
Status and results of a verify_list job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
my_contacts ~72
Search the key owner's own verified contacts (already paid for, never charged again). q matches name, title or company. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| domain | string | – | – |
| limit | integer | – | – |
| min_stars | number | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
verify_emails ~88
Verdict per address, synchronous for up to 25 addresses: valid, invalid, catch_all (accept-all domain), unknown, dead_domain or bad_syntax, each with a reason and a 0-5 star rating. 1 credit per definitive verdict (valid or invalid); the rest are free. For more than 25 use verify_list.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | – |
No output schema declared.
No examples provided.
verify_list ~81
Re-verify a larger list (up to 5,000 addresses) as a background job. Same verdicts and pricing as verify_emails. Waits up to wait_seconds, then returns results or the job_id to resume with get_list.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | – |
| name | string | – | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
How do I install the ai.lakewave/lakewave-mcp server?
ai.lakewave/lakewave-mcp runs locally as a PyPI package, launched with uvx lakewave-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · lakewave-mcp
claude mcp add ai-lakewave-lakewave-mcp -- uvx lakewave-mcp
What is the ai.lakewave/lakewave-mcp server?
ai.lakewave/lakewave-mcp is listed in the public MCP registry as ai.lakewave/lakewave-mcp. Verified B2B contacts at named accounts, email verdicts, contract signals and drafted campaigns. This page covers its PyPI package (lakewave-mcp).
Is the ai.lakewave/lakewave-mcp server safe to use?
ai.lakewave/lakewave-mcp scores 46 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 ai.lakewave/lakewave-mcp server expose?
ai.lakewave/lakewave-mcp exposes 11 tools: account, find_people, get_job, verify_emails, verify_list, and 6 more. Their descriptions and schemas cost roughly 901 tokens of context every time the server is loaded.
Is the ai.lakewave/lakewave-mcp server still maintained?
ai.lakewave/lakewave-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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 ai.lakewave/lakewave-mcp server under?
ai.lakewave/lakewave-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.