Remote MCP · Endpoint

Uk Tribunals MCP server

No. Uk Tribunals answered an MCP handshake 20 hours ago.

UpLast checked 20 hours ago

Server URL

https://gateway.pipeworx.io/uk-tribunals/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/uk-tribunals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
UK first-tier tribunal decisions — GOV.UK search + content API.
Listing
From the official MCP registry (active).
Recent checks of Uk Tribunals
CheckedResultHandshake
20 hours agoHandshake completed81 ms
2 days agoHandshake completed50 ms
5 days agoHandshake completed57 ms
6 days agoHandshake completed102 ms
8 days agoHandshake completed90 ms
9 days agoHandshake completed3.17 s
10 days agoHandshake completed814 ms
13 days agoHandshake completed1.14 s
14 days agoHandshake completed545 ms
16 days agoHandshake completed356 ms
18 days agoHandshake completed1.03 s
19 days agoHandshake completed51 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed37 ms
21 days agoHandshake completed55 ms

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