Lakewave MCP server

Read from the package source without running it. The installed server may list more.

• account

  Plan, remaining credits, prices and request limits for this API key.

• contracts_ending

  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.

• create_campaignwrite action

  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.

• email_formatwrite action

  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.

• find_people

  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. Cost

• get_campaign

  Campaign rollup: company statuses, draft / approved / sent counts, drafting progress.

• get_job

  Status and results of a find_people job. People are included once the job is done.

• get_list

  Status and results of a verify_list job.

• my_contacts

  Search the key owner's own verified contacts (already paid for, never charged again). q matches name, title or company. Free.

• verify_emails

  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.

• verify_list

  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.

• Code scan11 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

58/100

higher than 13% of 916 Email servers

Tools

11

the typical Email server has 7

Tools that change things

18%

typical: 25%. Fewer write tools means less an agent can break

Downloads a week

68

more than 49% of 235 Email servers with a package

Lakewave: common questions

Is Lakewave MCP server safe?

With care: it is graded C, so read the findings first (58/100). Read the Lakewave safety report

How do I install Lakewave?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Lakewave need an API key?

Yes. The registry entry asks for LAKEWAVE_API_KEY.

Is Lakewave maintained?

The latest release is v1.0.1.

What can I use instead of Lakewave?

Servers from other publishers that do the same job: MisarMail MCP Server, Nitrosend MCP server and e2a — email for AI agents MCP server.

How does Lakewave compare with other Email MCP servers?

safety score 58/100 (higher than 13% of 916 Email servers); tools 11 (the typical Email server has 7); tools that change things 18% (typical: 25%. Fewer write tools means less an agent can break). Full comparison.