Remote MCP · Endpoint

Scotcourts MCP server

No. Scotcourts answered an MCP handshake 18 hours ago.

UpLast checked 18 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/scotcourts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Scottish Courts and Tribunals Service (SCTS) — judgment search.
Listing
From the official MCP registry (active).
Recent checks of Scotcourts
CheckedResultHandshake
18 hours agoHandshake completed78 ms
2 days agoHandshake completed65 ms
4 days agoHandshake completed64 ms
6 days agoHandshake completed50 ms
8 days agoHandshake completed80 ms
9 days agoHandshake completed224 ms
10 days agoHandshake completed40 ms
13 days agoHandshake completed291 ms
14 days agoHandshake completed56 ms
16 days agoHandshake completed59 ms
18 days agoHandshake completed76 ms
19 days agoHandshake completed41 ms
20 days agoHandshake completed41 ms
21 days agoHandshake completed45 ms
21 days agoHandshake completed43 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 Scotcourts and makes no claim about it beyond what these checks measured.