Remote MCP · Endpoint

The Cable Code MCP server

No. The Cable Code answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://thecablecode.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.exquad/thecablecode
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
386 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Decode cables in 71 coding systems; design, rate, check, find equivalents; drums, laying, fire.
Listing
From the official MCP registry (active).
Recent checks of The Cable Code
CheckedResultHandshake
17 minutes agoHandshake completed386 ms
9 days agoHandshake completed444 ms
9 days agoHandshake completed202 ms
11 days agoHandshake completed198 ms
12 days agoHandshake completed683 ms
13 days agoHandshake completed205 ms
14 days agoHandshake completed272 ms
14 days agoHandshake completed447 ms
16 days agoHandshake completed423 ms
19 days agoHandshake completed570 ms
21 days agoHandshake completed175 ms
24 days agoHandshake completed384 ms
26 days agoHandshake completed411 ms
28 days agoHandshake completed183 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 The Cable Code and makes no claim about it beyond what these checks measured.