Remote MCP · Endpoint

Jwt MCP server

No. Jwt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/jwt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
196 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
JWT decoder MCP.
Listing
From the official MCP registry (active).
Recent checks of Jwt
CheckedResultHandshake
1 hour agoHandshake completed196 ms
21 hours agoHandshake completed273 ms
2 days agoHandshake completed128 ms
3 days agoHandshake completed111 ms
4 days agoHandshake completed65 ms
5 days agoHandshake completed121 ms
6 days agoHandshake completed79 ms
8 days agoHandshake completed121 ms
11 days agoHandshake completed72 ms
13 days agoHandshake completed138 ms
16 days agoHandshake completed93 ms
18 days agoHandshake completed155 ms
20 days agoHandshake completed68 ms
22 days agoHandshake completed63 ms
24 days agoHandshake completed54 ms
26 days agoHandshake completed53 ms
27 days agoHandshake completed59 ms
29 days agoHandshake completed53 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 Jwt and makes no claim about it beyond what these checks measured.