Remote MCP · Endpoint

Fjc Judges MCP server

No. Fjc Judges answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://gateway.pipeworx.io/fjc-judges/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fjc-judges
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
493 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
FJC Judges — the Federal Judicial Center's Biographical Directory of Article III federal judges…
Listing
From the official MCP registry (active).
Recent checks of Fjc Judges
CheckedResultHandshake
43 minutes agoHandshake completed493 ms
8 days agoHandshake completed438 ms
9 days agoHandshake completed72 ms
11 days agoHandshake completed587 ms
12 days agoHandshake completed93 ms
13 days agoHandshake completed106 ms
14 days agoHandshake completed240 ms
15 days agoHandshake completed277 ms
16 days agoHandshake completed557 ms
19 days agoHandshake completed52 ms
22 days agoHandshake completed114 ms
24 days agoHandshake completed67 ms
26 days agoHandshake completed82 ms
28 days agoHandshake completed80 ms

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

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