local-leads-mcp
Discovers local businesses needing a website via OpenStreetMap and verifies their leads with checks like website existence, email deliverability, and site quality scoring.
README
local-leads-mcp
<!-- mcp-name: io.github.Raffaele86/local-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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.