Website Contacts
LiveFind public contact details on a site's own pages.
Read a public site page and up to three same-site contact or about pages, then collect visible email addresses, click-to-call numbers and social profile links. It respects robots.txt and never visits the social platforms or sends a message.
Server URL
https://toolcargo.com/mcp/website-contactsClaude Code
claude mcp add --transport http --scope user toolcargo-website-contacts https://toolcargo.com/mcp/website-contacts \
--header "Authorization: Bearer YOUR_API_KEY"Create a key in your dashboard. Other clients: setup guides.
What it helps you do
- Visible public emails
- Click-to-call numbers
- Linked social profiles
Built for: Sales and partnership teams verifying how to contact a business.
Example requests
Partner research
“Find public contact details on https://example.com with ToolCargo.”
Emails, phone links and social profile URLs found on up to four allowed pages, with source pages listed.
Step-by-step workflows: pre-launch check · fixing link previews
Tools
| Tool | What it does | Access |
|---|---|---|
find_website_contactsFind website contacts | Read up to four public pages on one site, respecting robots.txt, to find visible email addresses, click-to-call numbers and social profile links. No message is sent. | Read-only |
Requirements
- • A ToolCargo account with Site Audit activated (free).
- • Public pages that allow our user agent in robots.txt.
Limitations
- • HTML only; JavaScript-rendered contacts may be missed.
- • Maximum four pages, each at most 500 KB. Redirects and unknown robots policy are refused.
- • Contact details are not validated or messaged.
Supported clients
“Tested” means we connected that client to this endpoint and ran a tool call ourselves. “Documented” means the client supports this setup per its own docs, but we have not tested it yet.
| Claude Code | API key header | Tested | Remote HTTP server with an Authorization header. Tested 2026-09-11 (v2.1.268). |
| Claude (claude.ai) | OAuth sign-in | Tested | Custom connector with OAuth sign-in; tested on claude.ai web 2026-09-11. Desktop and mobile use the same account connectors but were not tested separately. |
| Cursor | API key header | Documented, not yet tested | mcp.json with url and headers. |
| VS Code (Copilot agent mode) | API key header | Documented, not yet tested | .vscode/mcp.json with type http and headers. |
| ChatGPT (developer mode) | OAuth sign-in | Documented, not yet tested | Requires OAuth; API keys cannot be entered. |
| MCP Inspector | API key header | Tested | CLI mode, tested 2026-09-11. Useful for calling tools directly. |
More in SEO
- Accessibility Quick Audit LiveFind actionable accessibility issues in served HTML.
- DNS & email auth LiveSPF, DMARC, MX and DKIM lookups before a client domain goes live.
- Domain lookup LiveRegistrar, nameservers and expiry from public RDAP.
- HTTP headers LiveHSTS, CSP, cookies flags — what the server actually sends.
Pricing
Included with Site Audit. Each search is one call.
Free
$0For trying the connector on your own sites.
50 calls/month · 25 links per check
Pro
$12/moFor freelancers and agencies auditing client sites every week.
2,000 calls/month · 100 links per check
Proposed test price. See the pricing page for checkout status.