ContactLint MCP server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ContactLint MCP serveris jane@gmial.com valid? suggest the correct address"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ContactLint MCP server
ContactLint is a hosted MCP server that checks email addresses and phone numbers before your agent saves or uses them. It runs at a public URL, so there is nothing to install.
Endpoint:
https://contactlint.com/mcp(Streamable HTTP, JSON-RPC over POST)Website: https://contactlint.com/
OpenAPI (REST API): https://contactlint.com/openapi.json
MCP Registry:
com.contactlint/contactlint
This repository holds the listing files only (this README, server.json and a client config example). The server itself is hosted by ContactLint.
Tools
Tool | Input | What it does |
|
| Checks syntax, MX and A records over DNS-over-HTTPS, known disposable domains, role addresses (admin@, no-reply@) and free providers, and suggests a fix when the domain looks like a typo of a major provider (gmial.com). |
|
| Same checks as |
|
| Parses and validates a phone number: valid and possible flags, line type, region, E.164, national and international formats. |
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 needs an API key.
Related MCP server: Email Verifier MCP Server
Configuration
One setting is required:
Name | Required | Description |
| yes | Your ContactLint API key. Get a free key at https://contactlint.com/signup |
Send it as an Authorization: Bearer <apiKey> header (an x-api-key header also works).
Example client config (see examples/mcp.json):
{
"mcpServers": {
"contactlint": {
"type": "http",
"url": "https://contactlint.com/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}examples/config-schema.json describes the apiKey setting as JSON Schema, for directories and clients that ask for one.
Billing
One check per address or number checked. A
validate_emailscall with 20 addresses uses 20 checks.Addresses whose DNS lookup fails come back
unknownand are not billed.If a key does not have enough checks for a whole
validate_emailslist, 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
MIT, see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Verify addresses, email addresses, and phone numbers with confidence scores.
Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes.
Email intelligence for agents: MX, SPF/DKIM/DMARC, disposable/role checks, and a 0-100 score.
Verify emails, validate phone numbers, look up carriers and score IP addresses.
Related MCP Servers
- FlicenseAqualityCmaintenanceEnables agents to verify postal addresses, email addresses, and phone numbers against Melissa's Global Verification APIs before acting on the data, including batch verification and a per-session call budget to prevent runaway costs.4-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to verify email addresses in real-time, checking syntax, DNS, MX records, and SMTP handshake, returning verdicts and deliverability scores without sending actual emails.-
- AlicenseAqualityBmaintenanceEnables agents to validate and normalize phone numbers, email addresses, and postal addresses with production-grade, country-specific rules, including formatting, typo detection, and checks for disposable domains or fictional numbers.31MIT
- AlicenseAqualityBmaintenanceEnables agents to validate email addresses through RFC 5321 syntax checks, MX record lookups, a 182,000-domain disposable blacklist, role-account detection, and an optional SMTP handshake. Runs locally via npx or as a hosted HTTP endpoint, returning explainable per-check scores at zero per-lookup API cost.4MIT