Is the Contactlint MCP server down?

mcp-registry/com.contactlint/contactlint · v1.0.0

Also listed as github/zksyncer/contactlint

healthy
Last checked 2026-10-26 21:21 UTC · handshake 106ms

As of 2026-10-26 21:21 UTC, the Contactlint MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
2,413
outages (90d)
0
tools
3

Validate emails (MX, disposable, role, typo) and phone numbers, singly or in batches, for AI agents.

Point your MCP client at this streamable-http endpoint: https://contactlint.com/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 2 warning(s) across 3 tool(s); ~332 tokens of tool definitions.
Scores higher than 5% of 15,763 MCP servers Glimind has audited.
Its tool list costs an agent ~332 tokens per session — lighter than 95% of servers.
70 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

3 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: validate_email, validate_emails, validate_phone

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: validate_email, validate_emails, validate_phone

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.contactlint%2Fcontactlint/fixes

validate_email 1 change 
{
  "name": "validate_email",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "email": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
validate_emails 1 change 
{
  "name": "validate_emails",
  "description": "Check 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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "emails"
    ],
    "properties": {
      "emails": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 50,
        "minItems": 1
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
validate_phone 1 change 
{
  "name": "validate_phone",
  "description": "Parse and validate a phone number: valid, possible, type, region, E.164 and national formats. Uses 1 check.",
  "inputSchema": {
    "type": "object",
    "required": [
      "phone"
    ],
    "properties": {
      "phone": {
        "type": "string"
      },
      "country": {
        "type": "string",
        "description": "ISO 3166-1 alpha-2 default region, e.g. US"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.contactlint/contactlint"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.contactlint/contactlint"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.contactlint%2Fcontactlint.svg)](https://glimind.com/server/mcp-registry%2Fcom.contactlint%2Fcontactlint?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.contactlint%2Fcontactlint?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.contactlint%2Fcontactlint.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.contactlint%2Fcontactlint.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.contactlint%2Fcontactlint?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:425842aaacbe9413…, first seen 2026-10-17, included at leaf 18691 of 75,507. Version history · verify what your client received.

Tools (3)

Compare: most reliable email servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Contactlint MCP server down right now?

As of 2026-10-26 21:21 UTC, the Contactlint MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Contactlint MCP server provide?

Contactlint MCP server advertises 3 tools, including validate_email, validate_emails, validate_phone.

How do I install Contactlint MCP server?

Point your MCP client at this streamable-http endpoint: https://contactlint.com/mcp

Is the Contactlint MCP server safe to connect to an AI agent?

Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Contactlint MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve