Remote MCP · Endpoint

BizVerify MCP server

No. BizVerify answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
71 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 18 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
1 hour agoHandshake completed71 ms
1 day agoHandshake completed77 ms
2 days agoHandshake completed65 ms
3 days agoHandshake completed66 ms
4 days agoHandshake completed65 ms
5 days agoHandshake completed148 ms
7 days agoHandshake completed703 ms
10 days agoHandshake completed65 ms
12 days agoHandshake completed166 ms
14 days agoHandshake completed73 ms
17 days agoHandshake completed123 ms
19 days agoHandshake completed90 ms
21 days agoHandshake completed74 ms
23 days agoHandshake completed91 ms
25 days agoHandshake completed85 ms
26 days agoHandshake completed59 ms
28 days agoHandshake completed106 ms
29 days agoHandshake completed378 ms

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

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.