ContactLint
Validate emails (syntax, MX, disposable, role, typo) and phone numbers before your agent saves them.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~163Tokens (tool definitions)
~368 BTypical response size
Minimal attention impact (0.13% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"contactlint": {
"url": "https://contactlint.com/mcp"
}
}
}Remote endpoints
https://contactlint.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢validate_email(email)
Check 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.
Input Schema
{
"type": "object",
"properties": {
"email": {
"type": "string"
}
},
"required": [
"email"
]
}🟢validate_phone(phone, country)
Parse and validate a phone number: valid, possible, type, region, E.164 and national formats. Uses 1 check.
Input Schema
{
"type": "object",
"properties": {
"phone": {
"type": "string"
},
"country": {
"type": "string",
"description": "ISO 3166-1 alpha-2 default region, e.g. US"
}
},
"required": [
"phone"
]
}Community
Evidence
Recent observations
verifiedversion not recorded2 tools