Remote MCP · Endpoint

VerixID Verifier MCP server

No. VerixID Verifier answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.verixid.com/

The last check completed an MCP handshake.

Registry name
com.verixid/verifier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
193 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verify VerixID proof-of-existence records and optionally prove ownership.
Listing
From the official MCP registry (active).
Recent checks of VerixID Verifier
CheckedResultHandshake
1 hour agoHandshake completed193 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed139 ms
5 days agoHandshake completed185 ms
7 days agoHandshake completed233 ms
8 days agoHandshake completed389 ms
9 days agoHandshake completed182 ms
12 days agoHandshake completed148 ms
13 days agoHandshake completed81 ms
15 days agoHandshake completed186 ms
16 days agoHandshake completed370 ms
18 days agoHandshake completed140 ms
19 days agoHandshake completed33 ms
20 days agoHandshake completed169 ms
20 days agoHandshake completed165 ms
21 days agoHandshake completed70 ms
22 days agoHandshake completed661 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 VerixID Verifier and makes no claim about it beyond what these checks measured.