Remote MCP · Endpoint

Wiza MCP server

No. Wiza answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/wiza/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/wiza
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
249 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Wiza MCP — wraps the Wiza 'Individual Reveal' phone-lookup API (wiza.co)
Listing
From the official MCP registry (active).
Recent checks of Wiza
CheckedResultHandshake
1 hour agoHandshake completed249 ms
19 hours agoHandshake completed98 ms
2 days agoHandshake completed1.21 s
3 days agoHandshake completed867 ms
4 days agoHandshake completed321 ms
5 days agoHandshake completed728 ms
6 days agoHandshake completed399 ms
8 days agoHandshake completed1.53 s
10 days agoHandshake completed664 ms
13 days agoHandshake completed1.19 s
15 days agoHandshake completed113 ms
18 days agoHandshake completed2.57 s
19 days agoHandshake completed79 ms
22 days agoHandshake completed2.44 s
24 days agoHandshake completed1.74 s
25 days agoHandshake completed955 ms

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