Remote MCP · Endpoint

io.github.hellosg/coderegistry MCP server

No. io.github.hellosg/coderegistry answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://integrator.app.thecoderegistry.com/api/ai/router

The last check completed an MCP handshake.

Registry name
io.github.hellosg/coderegistry
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
64 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free.
Listing
From the official MCP registry (active).
Recent checks of io.github.hellosg/coderegistry
CheckedResultHandshake
1 hour agoHandshake completed64 ms
2 days agoHandshake completed48 ms
4 days agoHandshake completed84 ms
5 days agoHandshake completed63 ms
7 days agoHandshake completed35 ms
8 days agoHandshake completed42 ms
9 days agoHandshake completed50 ms
12 days agoHandshake completed285 ms
13 days agoHandshake completed53 ms
15 days agoHandshake completed50 ms
17 days agoHandshake completed41 ms
18 days agoHandshake completed41 ms
19 days agoHandshake completed50 ms
20 days agoHandshake completed46 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed71 ms
23 days agoHandshake completed68 ms

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

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 io.github.hellosg/coderegistry and makes no claim about it beyond what these checks measured.