About local-leads-mcp
local-leads-mcp helps freelancers and agencies find local businesses through OpenStreetMap and check their websites, email deliverability, and site quality. It includes the underlying checks for its findings, and its core workflow needs no API keys.
Key features
- 01Find local businesses by area and category
- 02Check website status and whether it is an owned site
- 03Pre-check email deliverability through MX records
- 04Score websites using named issues
- 05Export CSV, JSON, or Markdown
Use cases
- 01Find businesses in an area without their own websites
- 02Filter false positives in website-status checks
- 03Check a business's email domain before outreach
- 04Organize and export verified leads
MCP support
The MCP server exposes tools for business discovery, website verification, MX checks, site scoring, lead confirmation, and export. The core workflow needs no API key; confirming no website through Brave or Google search and adding PageSpeed scores require the corresponding keys.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx local-leads-mcpBRAVE_API_KEYSecretBrave Search API key (enables confirm_no_website)GOOGLE_CSE_API_KEYSecretGoogle Programmable Search API key (alternative to Brave)GOOGLE_CSE_CXGoogle Programmable Search engine id (used with GOOGLE_CSE_API_KEY)PAGESPEED_API_KEYSecretGoogle PageSpeed Insights API key (adds Lighthouse scores to score_website)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMElocal-leads-mcp
Find local businesses that need a website — and prove it — from your AI agent.
One MCP server that discovers local businesses via OpenStreetMap and then verifies them with the checks that separate a real lead list from a pile of false positives. Built for freelancers and agencies that use Claude, Cursor or any MCP client for prospecting.
No API keys required for the core workflow: discovery, website verification, email deliverability check and weak-site scoring all run on free, open infrastructure (Overpass, Nominatim, DNS-over-HTTPS, plain HTTP).
Why this and not a maps scraper?
The hard part of local prospecting isn't getting a list of businesses — it's not embarrassing yourself. Lead lists built from raw map data are full of traps this server checks for explicitly:
- "No website" that isn't. OSM data can be stale; a missing
websitetag proves nothing.verify_websitechecks apex and www and redirects (an apex domain that doesn't resolve while the site lives happily onwww.is a classic false "no website"), andconfirm_no_websiteuses a web search as the final word. - A Facebook page is not a website. Social profiles, booking aggregators (Fresha, TheFork, Treatwell…), directory listings and free subdomains (
*.wixsite.com,*.business.site…) are classified asnot_own_site, not as "has a website". - Emails that bounce.
check_mxpredicts deliverability before you ever write to a lead (no MX = guaranteed bounce; PEC-only domains are flagged). - "The site is bad" needs evidence.
score_websitereturns citable issues (no HTTPS, no mobile viewport, missing title/meta/H1, no sitemap…), not vibes — optionally with Lighthouse scores via the PageSpeed API.
Every verdict ships with the raw checks that produced it, so your agent can show its work.
Quickstart (60 seconds)
{
"mcpServers": {
"local-leads": {
"command": "uvx",
"args": ["local-leads-mcp"]
}
}
}
That's it — no credentials. Then ask your agent things like:
Find 20 restaurants in Turin with no website, verify each one, and give me a CSV of the confirmed ones with a phone number.
Optional environment variables
| Variable | Enables |
|---|---|
BRAVE_API_KEY | confirm_no_website via Brave Search API |
GOOGLE_CSE_API_KEY + GOOGLE_CSE_CX | confirm_no_website via Google Programmable Search |
PAGESPEED_API_KEY | Lighthouse scores inside score_website |
Tools
Discovery (OpenStreetMap — no key)
find_businesses(area, category, website_filter, phone_prefix, require_phone, limit)— businesses in a city/district, filtered by website presence. ~35 friendly categories plus any raw OSMkey=valuetag.list_categories()— the category → OSM tag map.
Verification (no key)
verify_website(domain_or_url)— verdicts:live_own_site,not_own_site,domain_exists_no_site,no_website_found; includes per-URL evidence.check_mx(domain)— email deliverability pre-check via DNS-over-HTTPS.
Qualification (no key; PageSpeed optional)
score_website(url)— 0–100 weak-site score with named issues + CMS/tech detection (WordPress, Wix, Shopify, …).
Confirmation (needs a search key)
confirm_no_website(business_name, city)— the final word on "really no website?", classifying search results into own-site candidates vs listings/socials.
Export
export_leads(leads_json, format)— CSV, JSON or Markdown table.
Ethics & fair use
- Data sources are public: OpenStreetMap (© OSM contributors, ODbL), public DNS, and the businesses' own public pages.
- OSM requests are rate-limited locally (min 1 s between calls) and carry a descriptive User-Agent, per the Nominatim and Overpass usage policies. For heavy workloads, run your own Overpass instance.
- This server discovers and verifies — it does not scrape personal emails and it does not send anything. How you contact a business is on you: follow your local rules (GDPR and friends).
See also
seo-stack-mcp — the same idea for SEO data: Google Search Console, GA4, Bing Webmaster and Microsoft Clarity in one MCP server. Prospect with local-leads, then monitor the sites you build with seo-stack.
License
MIT.
Built by Raffaele Nocera — web consulting for local businesses. If this tool helps you win a client, I'd love to hear about it.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.