Remote MCP · Endpoint

Didit MCP server

No. Didit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/didit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
101 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Didit MCP — wraps the Didit v3 identity / compliance API (didit.me)
Listing
From the official MCP registry (active).
Recent checks of Didit
CheckedResultHandshake
1 hour agoHandshake completed101 ms
1 day agoHandshake completed187 ms
2 days agoHandshake completed148 ms
3 days agoHandshake completed106 ms
4 days agoHandshake completed57 ms
5 days agoHandshake completed114 ms
6 days agoHandshake completed96 ms
8 days agoHandshake completed80 ms
11 days agoHandshake completed241 ms
13 days agoHandshake completed77 ms
16 days agoHandshake completed89 ms
18 days agoHandshake completed74 ms
20 days agoHandshake completed69 ms
22 days agoHandshake completed117 ms
24 days agoHandshake completed78 ms
26 days agoHandshake completed50 ms
27 days agoHandshake completed81 ms
29 days agoHandshake completed47 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 Didit and makes no claim about it beyond what these checks measured.