ContactLint MCP server
online · 100% uptimecom.contactlint/contactlint·v1.1.0Validate emails (MX, disposable, role, typo) and phone numbers, singly or in batches, for AI agents.
0 stars
Reviews
Write oneNobody has reviewed ContactLint yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ContactLint tools (3, 1 write)
write = sends, deletes, buys or postsvalidate_emailwrite actionFreeCheck an email address: syntax, MX/A records via DNS-over-HTTPS, disposable domain, role address, free provider, typo suggestion for major providers. No SMTP probing. Uses 1 check.
validate_emailsFreeCheck a list of up to 50 email addresses in one call, with the same checks as validate_email. Returns one result per address in the same order plus a summary of verdicts. Uses 1 check per address; addresses whose DNS lookup fails come back with reason dns_error and are not billed. If the key lacks checks for the whole list, nothing is checked or billed.
validate_phoneFreeParse and validate a phone number: valid, possible, type, region, E.164 and national formats. Uses 1 check.
Public scan report
scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 478ms20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How ContactLint compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 106 ms
- faster than 83% of 30,031 servers
What its tools let an agent do: 2 read · 1 change
Install ContactLint in Claude Code, Cursor or VS Code
claude mcp add --transport http contactlint https://contactlint.com/mcp
What the publisher says
From the ContactLint repository's README, as published. We do not edit it. Read it on GitHub
ContactLint MCP Server (contactlint-mcp)
ContactLint checks email addresses and phone numbers before your AI agent saves or uses them. You can run it as a local stdio MCP server (contactlint-mcp, reading CONTACTLINTAPIKEY from the environment) or connect directly to the hosted Streamable HTTP endpoint (https://contactlint.com/mcp).
- Local stdio binary: contactlint-mcp (./bin/contactlint-mcp.mjs)
- Hosted endpoint: https://contactlint.com/mcp (Streamable HTTP, JSON-RPC over POST)
- Website: https://contactlint.com/
- MCP guide: https://contactlint.com/email-validation-mcp-server
- OpenAPI (REST API): https://contactlint.com/openapi.json
- MCP Registry: com.contactlint/contactlint
Tools
ContactLint does not connect to mail servers (no SMTP probing), so it cannot confirm that a mailbox exists or detect catch-all domains.
initialize and tools/list work without a key, so clients and directory scanners can read the tool list. tools/call requires a ContactLint API key (100 free checks per month, no card required).
Option 1: Local stdio MCP server (recommended for registries & desktop clients)
The local stdio server (bin/contactlint-mcp.mjs) reads your API key from the CONTACTLINTAPIKEY secret environment variable and forwards authenticated tool calls to https://contactlint.com/mcp.
Environment variables
Client configuration (stdio via npx)
{
"mcpServers": {
"contactlint": {
"command": "npx",
"args": ["-y", "github:zksyncer/contactlint"],
"env": {
"CONTACTLINT_API_KEY": "YOUR_API_KEY"
}
}
}
}Or when installed locally (npm install -g github:zksyncer/contactlint or pnpm add contactlint-mcp):
{
"mcpServers": {
"contactlint": {
"command": "contactlint-mcp",
"env": {
"CONTACTLINT_API_KEY": "YOUR_API_KEY"
}
}
}
}Option 2: Hosted Streamable HTTP MCP server
If your MCP client supports custom HTTP headers on remote streamable-http servers, you can connect directly without installing anything:
{
"mcpServers": {
"contactlint": {
"type": "http",
"url": "https://contactlint.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Billing
- One check per address or number checked. A validate_emails call with 20 addresses uses 20 checks.
- Addresses whose DNS lookup fails come back unknown (dns_error) and are not billed.
- If a key does not have enough checks for a whole validate_emails list, nothing is checked or billed.
- 100 checks per month are free, no card needed.
- Credit packs: 5,000 checks for $9, 25,000 for $35, 100,000 for $99.
Free tools
Free browser tools (disposable email checker, phone number validator, disposable domain list) are at https://contactlint.com/tools
License
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
ContactLint: common questions
- Is ContactLint MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the ContactLint safety report
- How do I install ContactLint?
- It runs remotely at contactlint.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does ContactLint need an API key?
- Yes. The registry entry asks for
Authorization. - Is ContactLint maintained?
- The last commit was 10 days ago (2026-10-25). The latest release is v1.1.0.
- Is ContactLint up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does ContactLint compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.