Remote MCP · Endpoint

UK Data: Code utilities MCP server

No. UK Data: Code utilities answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ukdata.reliness.co.uk/mcp/code-utilities

The last check completed an MCP handshake.

Registry name
uk.co.reliness/code-utilities
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
64 ms
Tools exposed
32 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Deterministic string, list and number routines: palindromes, sorting, searching, validation, merging
Listing
From the official MCP registry (active).
Recent checks of UK Data: Code utilities
CheckedResultHandshake
1 hour agoHandshake completed64 ms
4 days agoHandshake completed472 ms
7 days agoHandshake completed474 ms

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

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 Data: Code utilities and makes no claim about it beyond what these checks measured.