Remote MCP · Endpoint

Zovo NPI Lookup MCP server

No. Zovo NPI Lookup answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://npi-lookup.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/npi-lookup
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
388 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Provider rosters & NPI checks
Listing
From the official MCP registry (active).
Recent checks of Zovo NPI Lookup
CheckedResultHandshake
44 minutes agoHandshake completed388 ms
3 days agoHandshake completed133 ms
13 days agoHandshake completed307 ms
13 days agoHandshake completed411 ms
15 days agoHandshake completed265 ms
15 days agoHandshake completed165 ms
17 days agoHandshake completed203 ms
18 days agoHandshake completed322 ms
18 days agoHandshake completed149 ms
20 days agoHandshake completed362 ms
22 days agoHandshake completed147 ms
25 days agoHandshake completed271 ms
27 days agoHandshake completed230 ms

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

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