Server data from the Official MCP Registry
Domain to public business contacts: role emails, phones, socials, company name and address.
About
Domain to public business contacts: role emails, phones, socials, company name and address.
Remote endpoints: streamable-http: https://mcp.apify.com/?tools=fetch-actor-details,fairquery/website-contact-company-enricher
Security Report
Valid MCP server (3 strong, 3 medium validity signals). 3 known CVEs in dependencies (2 critical, 0 high severity) Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 4 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-fairquery-website-contact-company-enricher": {
"url": "https://mcp.apify.com/?tools=fetch-actor-details,fairquery/website-contact-company-enricher"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Website Contact & Company Enricher
Turns company domains into one row each (public business emails, phones, social profiles, company name and address) for $3 per 1,000 domains. You pay $0.003 per domain that returns a result row, and unreachable, blocked or invalid domains are free. Example: enriching 500 domains costs at most 500 × $0.003 = $1.50, plus Apify's $0.00005 Actor-start fee.
Fairquery Apify Actor that turns a list of domains into one clean row per company: business emails (validated for MX, disposable domains and typos), phone numbers (E.164), social profiles, company name, description and postal address, taken from the homepage and its contact / about / imprint pages. Plain HTTP, no browser, robots.txt respected, one request at a time per site.
When to use this Actor (LLM / tool selection)
Use it when an agent or sales-ops workflow needs to:
- Add a contact email, phone and LinkedIn company page to a list of company websites (CRM enrichment, lead lists, vendor onboarding)
- Find the generic inbox (
info@,sales@,support@,press@) of a company and check that its domain actually receives mail - Get the legal company name and address from structured data or the imprint page (EU sites)
- Collect a company's official social accounts
Do not use it to find personal emails of individuals or to scrape people's profiles. By default it returns role / generic mailboxes only (emailScope: "role"); personal LinkedIn profiles (/in/…) are never returned.
How it works
- Normalises each input (
https://www.Acme.com/contact,jane@acme.com,acme.com→acme.com) and removes duplicates. - Reads
robots.txt(RFC 9309: missing = allowed, 5xx = disallowed) and honoursDisallowrules andCrawl-delayfor user agentFairqueryBot. - Fetches the homepage, then the best-scoring same-site pages (contact, Kontakt, contacto, about, imprint/Impressum, legal notice, team…) up to
maxPagesPerDomain, waitingrequestDelayMsbetween requests to the same site. - Extracts: JSON-LD
Organization/LocalBusiness(name, legalName, telephone, email, address, sameAs),mailto:andtel:links, Cloudflare-protected emails,name [at] domain [dot] comobfuscation,og:site_name,<address>blocks, social links. - Validates emails with the same code as Fairquery Email Validator: syntax, DNS-over-HTTPS MX/null-MX, disposable list, free-provider and typo checks (no SMTP probing).
Input
| Field | Type | Default | Description |
|---|---|---|---|
domains | string[] | (required) | Domains, URLs or emails |
maxPagesPerDomain | int | 5 | 1–15, homepage included |
emailScope | role | business | all | role | business adds named addresses on the company's own domain |
validateEmails | bool | true | MX / disposable / typo |
checkSpfDmarc | bool | false | SPF/DMARC for the company mail domain |
defaultPhoneCountry | string | – | e.g. US; also parse national-format numbers in page text |
domainConcurrency | int | 5 | Sites in parallel |
requestDelayMs | int | 1000 | Delay between requests to one site |
requestTimeoutSecs | int | 15 | Per request |
domainTimeoutSecs | int | 40 | Hard limit per domain (all pages + DNS). At the limit you get the data collected so far (partial: true), or an uncharged DOMAIN_TIMEOUT error row if the homepage never loaded |
maxDomains | int | 1000 | Safety cap |
{ "domains": ["apify.com", "stripe.com", "https://basecamp.com/"], "maxPagesPerDomain": 4 }
Output
{
"schema_version": "1.0.0", "type": "domain", "input": "apify.com", "domain": "apify.com", "final_url": "https://apify.com/",
"company_name": "Apify Technologies s.r.o.",
"description": "Cloud platform for web scraping, browser automation, AI agents, and data for AI…",
"emails": [
{ "email": "hello@apify.com", "source_url": "https://apify.com/contact", "is_role_account": true, "on_company_domain": true,
"is_free_provider": false, "is_disposable": false, "verdict": "valid", "reasons": ["ROLE_ACCOUNT"], "has_mx": true, "mail_provider": "Google Workspace / Gmail" }
],
"primary_email": "hello@apify.com",
"phones": [{ "e164": "+18889262289", "raw": "+1 888 926 2289", "source_url": "https://stripe.com/contact/sales", "source": "tel" }],
"social_links": { "linkedin": ["https://linkedin.com/company/apify"], "twitter": ["https://x.com/apify"], "github": ["https://github.com/apify"] },
"address": "Na Příkopě 959/27, 11000, Prague, CZ",
"mail_domain": { "has_mx": true, "null_mx": false, "mail_provider": "Google Workspace / Gmail", "has_spf": null, "has_dmarc": null, "dmarc_policy": null },
"pages_crawled": ["https://apify.com/", "https://apify.com/contact"], "pages_blocked_by_robots": 0, "robots_txt": "ok", "email_scope": "role"
}
Error rows (type: "error", never charged): INPUT_EMPTY, INVALID_DOMAIN, MAX_DOMAINS_EXCEEDED, SITE_UNREACHABLE, BLOCKED_BY_ROBOTS, ENRICH_FAILED, DOMAIN_TIMEOUT, RUN_TIMEOUT_NEAR.
RUN_SUMMARY (key-value store): pages fetched, pages blocked by robots.txt, emails found vs. excluded by scope, DNS requests, charged events.
Pricing
| Event | Price | When |
|---|---|---|
domain-enriched | $0.003 | Each domain that returns a result row |
apify-actor-start | $0.00005 | Once per run, per GB of memory (Apify default event) |
Error rows (SITE_UNREACHABLE, BLOCKED_BY_ROBOTS, INVALID_DOMAIN, ENRICH_FAILED, …) are never charged. A domain is charged once, however many pages are crawled (up to maxPagesPerDomain).
Worked example: 1,000 domains from a Google Maps export, of which 120 are unreachable or blocked: 880 × $0.003 = $2.64, plus $0.00005.
To cap spend, set a maximum cost per run in the run options; the Actor stops cleanly at the limit. maxDomains caps how many domains one run processes. Prices are from the Store pricing tab (October 2026).
Memory / runtime
Default 256 MB, no browser, no proxy. With the default politeness settings a domain takes about 3–8 s (homepage + 4 pages, 1 s apart), and 5 domains run in parallel, so 100 domains finish in roughly 1–3 minutes. Sites that block datacenter IPs or need JavaScript to render contact details will return fewer fields. Memory is capped at 512 MB (more does not help: the Actor is network-bound). Each domain has a hard 40 s time limit (domainTimeoutSecs), so one slow or tarpitting site can't hang the run, and every finished domain is saved and charged immediately. The default run timeout is 15 minutes (about 500–1,000 domains); shortly before the timeout the Actor stops starting new domains and adds an uncharged RUN_TIMEOUT_NEAR row listing how many were skipped, so split very large lists or raise the timeout.
MCP / Apify tools
Call from agents via Apify MCP with Actor fairquery/website-contact-company-enricher:
{ "actor": "fairquery/website-contact-company-enricher", "input": { "domains": ["acme.com"] } }
Local stdio MCP server
The mcp/ folder is a stdio MCP server (TypeScript, @modelcontextprotocol/sdk) with two tools, both with annotations and output schemas:
| Tool | What it does | Cost |
|---|---|---|
enrich_domains | Runs this Actor and returns the rows | Needs APIFY_TOKEN, billed per domain |
normalize_domains | Cleans URLs/emails into unique domains, lists invalid ones | Free, local, no token |
cd mcp && npm install && npm run build
node scripts/smoke-test.mjs # initialize + tools/list + free tool, no token
APIFY_TOKEN=... node scripts/smoke-test.mjs --call # real call
{ "mcpServers": { "fairquery-contact-enricher": { "command": "node", "args": ["/path/to/website-contact-company-enricher/mcp/dist/index.js"], "env": { "APIFY_TOKEN": "<your Apify token>" } } } }
Docker: the root Dockerfile builds the MCP server image (docker build -t fairquery-contact-enricher-mcp .); it is also the Dockerfile for Glama. The Actor image is .actor/Dockerfile. glama.json lists fairquery as maintainer.
Works well after
- Google Maps Scraper: pass the
websitecolumn intodomainsto add a generic inbox, phone, LinkedIn page and legal name to each business. - Google Search Results Scraper or any company list: domains, URLs and email addresses are all accepted and normalised.
- Next steps: re-check the emails with the Email Validator just before sending, and screen company names with the Sanctions & Watchlist Screener when you onboard suppliers or customers.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
Run is rejected because domains is required | The input had no domains. The three sample domains in the Console form are prefill only and are not sent with API calls. |
BLOCKED_BY_ROBOTS or few pages crawled | The site's robots.txt disallows FairqueryBot for those paths, and the Actor honours it. These rows are free. |
SITE_UNREACHABLE / no emails on a JavaScript-heavy site | The site blocks datacenter IPs or renders contact details with JavaScript. The Actor uses plain HTTP with no proxy or browser, so such sites return fewer fields. |
| Named people's emails missing | By default emailScope is role (info@, sales@ …). Use business to include named addresses on the company's own domain, but only if you have a lawful basis to process them. |
| Run slower than expected | Politeness settings: requestDelayMs (default 1,000 ms between requests to one site) and domainConcurrency (default 5). Raise concurrency rather than lowering the delay. |
FAQ
Where does the data come from?
Only from pages the company publishes on its own domain: homepage, contact, about, imprint and team pages, plus JSON-LD structured data. No third-party databases.
Does it return personal emails or LinkedIn profiles of people?
By default it returns role and generic mailboxes only, and personal LinkedIn profiles (/in/…) are never returned.
Are emails verified?
They are checked for syntax, MX/null-MX, disposable domains and typos (the same code as the Fairquery Email Validator). There is no SMTP probing, so a mailbox is never confirmed.
How much does it cost?
$0.003 per enriched domain ($3 per 1,000), plus a $0.00005 start fee. Unreachable, blocked and invalid domains are free.
How do I limit spend?
Set a maximum cost per run in the run options and/or lower maxDomains.
Is this GDPR-compliant?
The Actor only reads what businesses publish, but business contact data can still be personal data. You need a lawful basis, must honour opt-outs and must follow anti-spam law. See the disclaimer.
Fairquery family
Other Fairquery tools on the Apify Store. Each one returns structured rows with machine-readable error codes, and error rows are never charged:
- Email Validator for Agents (MX, Disposable, Typo): syntax, MX, disposable, role and typo checks without sending mail; $0.79 per 1,000 emails
- Website Tech, SEO & llms.txt Check for Agents: tech stack, SEO score, AI-crawler rules and llms.txt per site; $1.50 per 1,000 sites
- Sanctions & Watchlist Screener (OFAC, EU, UK, UN): fuzzy name screening against official sanctions lists; $3 per 1,000 names + $0.007 per run
- LLM Data Guard: PII & Secret Redactor: redact PII and secrets before text reaches an LLM; $1.50 per 1,000 documents + $0.20 per 1,000 findings
- Dependency Vulnerability Check for Agents: packages and lockfiles against OSV.dev; $0.50 per 1,000 packages + $1.50 per 1,000 vulnerabilities
- EDGAR Company Facts & Filings for Agents: SEC filings and XBRL facts by ticker, CIK or name; from $1.50 per 1,000 companies
- Company Jobs Feed: Greenhouse, Lever & Ashby: live jobs from employers' own ATS boards with age and repost signals; $0.99 per 1,000 jobs + $0.0005 per board
- Competitor Change Tracker: Pricing, Terms, Careers & Changelog: watch competitors' public pricing, terms, careers and changelog pages for real changes with plain-English summaries and webhook alerts; $0.00049 per page checked + $0.0049 per change
- AI Exposure Scanner: Public Secrets, Files & AI-Crawler Policy: passive, scored scan of your own domains and public GitHub repos for leaked secrets (masked), exposed files, AI-crawler policy, security headers and SPF/DMARC; $0.039 per domain + $0.0039 per repo + $0.0019 per finding
- MCP server
@fairquery/agent-trust-mcp: one MCP server for Claude Desktop, Cursor and VS Code (npx -y @fairquery/agent-trust-mcp). It has 7 free tools that need no token, plus paid tools that call the PII, email, sanctions and OSV Actors with your own Apify token.
All Fairquery Actors: https://apify.com/fairquery
Kits & templates
Optional guides from Fairquery for wiring this Actor into agents and automations (the Actor works fine without them):
- AI Agent Data Toolkit Quick-Start (PDF): MCP setup for Claude Desktop and Cursor, API calls, recipes, cost estimates.
- n8n + Zapier Workflow Template Pack: 10 importable n8n workflows for the four original Fairquery Actors (SEC EDGAR, website/tech, email, OSV); it does not include workflows for this Actor yet, but the patterns adapt easily.
- Agent Prompt Pack for Research & Lead Ops: 69 prompts for company research, lead cleaning, SEO and security reviews.
- Agent Starter Kit: 10 copy-paste MCP + n8n recipes ($5): 10 copy-paste MCP + n8n recipes, with ready-made Claude/Cursor configs and 3 starter workflows.
Disclaimer
Returns only information that companies publish on their own websites. You are responsible for how you use it: business contact data can still be personal data under GDPR/UK GDPR, so have a lawful basis, honour opt-outs, and follow anti-spam law (CAN-SPAM, ePrivacy/PECR) when you contact anyone. DNS checks cannot prove a mailbox exists.
Links
- Apify Store: https://apify.com/fairquery/website-contact-company-enricher
- GitHub: https://github.com/fairquery/website-contact-company-enricher
- Contact: fairquery@proton.me
- License: MIT
Development
Local development, tests and deployment notes are in DEVELOPMENT.md. The Apify Store README is .actor/README.md.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
