Headless Lead Scraping MCP Server
MCP server for real-time public-web lead research without search API keys, using Google Maps and web search engines with LLM-based extraction, crawling, and local lead storage/export.
README
Headless Lead Scraping MCP Server v0.4.0
A UI-free MCP server for real-time public-web lead research with no search API provider, no Tavily key, and no hosted scraping service.
What it does
- Searches Google Maps first (browser-rendered) for local places — returns name, address, phone, and official website.
- Then searches web search engines (Yahoo, DuckDuckGo, Bing) directly at request time, with no search API key.
- Then searches related search engines (Startpage, browser-rendered) as an extra fallback source.
- Fetches target websites directly over HTTP.
- Falls back to headless Chromium/Playwright for JavaScript-rendered pages.
- Crawls relevant internal contact/about/team/social pages.
- Uses the configured LLM through the Vercel AI SDK for structured extraction and verification.
- Deduplicates results and filters by required fields.
- Stores leads locally in
data/leads.jsonl. - Filters stored leads and exports them as CSV or JSON files.
- Exposes everything as MCP tools over stdio.
Data-source priority
Sources are tried in order until enough results are found:
- Google Maps (
googlemaps) — browser-renderedgoogle.com/maps/search/; best for local businesses/product companies (name, address, phone, website, rating). - Web search engines — Yahoo, DuckDuckGo, Bing (
yahoo,duckduckgo,bing). - Related search engines — Startpage (
startpage, browser-rendered) for additional coverage.
The order is configurable via SEARCH_ENGINES (comma-separated). Maps-related settings: MAPS_SEARCH_URL, MAPS_MAX_RESULTS.
No external data API
There is no Tavily, Bing Search API, Google Search API, SerpAPI, Apify, Bright Data, or hosted scraper in this version.
The server performs search by requesting normal public search-result webpages and Google Maps search pages directly. Engines that respond with a CAPTCHA or bot-challenge page are skipped automatically. This means there is no API account or API key for search, but a public search website is still necessarily involved: the open Internet has no universal built-in index that a standalone program can query without using some indexed search source or already-known URLs.
If a search website blocks automated requests, the server cannot and does not bypass CAPTCHA, login, paywalls, robots directives, rate limits, or access controls.
LLM
The only required AI dependency is your LLM endpoint. The server supports OpenAI-compatible endpoints, including:
- Ollama
- LM Studio
- OpenAI
- other OpenAI-compatible local/self-hosted endpoints
For maximum independence, use Ollama or LM Studio locally.
Playwright
Playwright is the browser engine, not a lead-data provider. It is used only when a normal HTTP fetch cannot obtain the rendered page content or when browser rendering is explicitly requested.
Install Chromium:
npm install
npx playwright install chromium
Install
cp .env.example .env
npm install
npx playwright install chromium
npm run build
npm start
For development:
npm run dev
Ollama
ollama pull qwen3
.env:
LLM_PROVIDER=ollama
LLM_MODEL=qwen3
LLM_BASE_URL=http://127.0.0.1:11434/v1
LLM_API_KEY=ollama
LM Studio
Start a local OpenAI-compatible server in LM Studio and set:
LLM_PROVIDER=lmstudio
LLM_MODEL=YOUR_LOADED_MODEL_ID
LLM_BASE_URL=http://127.0.0.1:1234/v1
LLM_API_KEY=lm-studio
MCP tools
search_web— live web search in priority order (Google Maps, then web engines, then related engines); optionalenginesparam.scrape_page— HTTP fetch + Playwright fallback.extract_leads— LLM extraction from supplied page content.find_leads— Google Maps place discovery first, then web + related engine search; crawls, extracts, verifies, deduplicates, filters byrequiredFields, stores.list_stored_leads— read locally stored records.filter_leads— filter stored leads by keyword, field presence, and minimum confidence.export_leads— write stored leads (optionally filtered) to a CSV or JSON file on disk.clear_stored_leads— clear local records.
Example
{
"query": "software development companies",
"location": "California, USA",
"limit": 25,
"requiredFields": ["name", "website", "email"],
"maxSearchQueries": 8
}
requiredFields filters out any lead missing all of the listed fields. Default is ["name"].
Export example:
{
"format": "csv",
"hasEmail": true,
"minConfidence": "medium",
"filename": "california-leads"
}
This writes data/california-leads.csv (or .json for format: "json") and returns the file path and row count.
Stored data
Default:
data/leads.jsonl
No hosted database is required. The file is local to the MCP server process.
Important limitation
A truly provider-free program cannot discover arbitrary Internet resources from nothing: search requires an index or known URLs. This project removes search APIs and hosted scraping providers and performs live search-page retrieval itself. It does not pretend that the Internet has a universal local index.
Only publicly accessible information is collected. The server does not bypass authentication, CAPTCHA, paywalls, robots/access controls, or other security mechanisms.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。