Remote MCP · Endpoint

TPSClear MCP server

No. TPSClear answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://tpsclear.co.uk/api/mcp

The last check completed an MCP handshake.

Registry name
uk.co.tpsclear/tpsclear
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
199 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Screen UK numbers against TPS and CTPS, wash AU numbers against the DNCR, check dead mobiles.
Listing
From the official MCP registry (active).
Recent checks of TPSClear
CheckedResultHandshake
34 minutes agoHandshake completed199 ms
9 days agoHandshake completed138 ms
10 days agoHandshake completed168 ms
11 days agoHandshake completed156 ms
12 days agoHandshake completed209 ms
14 days agoHandshake completed173 ms
14 days agoHandshake completed145 ms
15 days agoHandshake completed198 ms
17 days agoHandshake completed264 ms
19 days agoHandshake completed188 ms
21 days agoHandshake completed703 ms
24 days agoHandshake completed139 ms
26 days agoHandshake completed182 ms
28 days agoHandshake completed185 ms

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

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