Remote MCP · Endpoint

ContactLint MCP server

No. ContactLint answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://contactlint.com/mcp

The last check completed an MCP handshake.

Registry name
com.contactlint/contactlint
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Validate emails (MX, disposable, role, typo) and phone numbers, singly or in batches, for AI agents.
Listing
From the official MCP registry (active).
Recent checks of ContactLint
CheckedResultHandshake
6 hours agoHandshake completed90 ms
15 hours agoHandshake completed235 ms
1 day agoHandshake completed151 ms
3 days agoHandshake completed106 ms
4 days agoHandshake completed84 ms
4 days agoHandshake completed99 ms
5 days agoHandshake completed134 ms
7 days agoHandshake completed45 ms
8 days agoHandshake completed415 ms
11 days agoHandshake completed128 ms
13 days agoHandshake completed130 ms
16 days agoHandshake completed97 ms
18 days agoHandshake completed134 ms
20 days agoHandshake completed99 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with ContactLint and makes no claim about it beyond what these checks measured.