Remote MCP · Endpoint

BizVerify MCP server

No. BizVerify answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.bizverify.co/mcp

The last check completed an MCP handshake.

Registry name
co.bizverify/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
KYB for AI agents: verify business registrations from MCP clients.
Listing
From the official MCP registry (active).
Recent checks of BizVerify
CheckedResultHandshake
3 hours agoHandshake completed74 ms
2 days agoHandshake completed91 ms
4 days agoHandshake completed85 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed106 ms
8 days agoHandshake completed378 ms
9 days agoHandshake completed382 ms
12 days agoHandshake completed60 ms
13 days agoHandshake completed48 ms
15 days agoHandshake completed201 ms
16 days agoHandshake completed52 ms
17 days agoHandshake completed109 ms
18 days agoHandshake completed147 ms
19 days agoHandshake completed194 ms
20 days agoHandshake completed68 ms
21 days agoHandshake completed45 ms
22 days agoHandshake completed79 ms

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

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