Remote MCP · Endpoint

BillionVerify MCP server

No. BillionVerify answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://mcp.billionverify.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.BillionVerify/billionverify-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
156 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Email verification for AI agents: verify single or bulk emails, check credits and history.
Listing
From the official MCP registry (active).
Recent checks of BillionVerify
CheckedResultHandshake
13 minutes agoHandshake completed156 ms
9 days agoHandshake completed337 ms
9 days agoHandshake completed172 ms
11 days agoHandshake completed375 ms
12 days agoHandshake completed187 ms
13 days agoHandshake completed407 ms
14 days agoHandshake completed176 ms
15 days agoHandshake completed142 ms
16 days agoHandshake completed174 ms
19 days agoHandshake completed327 ms
21 days agoHandshake completed142 ms
24 days agoHandshake completed157 ms
26 days agoHandshake completed369 ms
28 days agoHandshake completed148 ms

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

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 BillionVerify and makes no claim about it beyond what these checks measured.