Remote MCP · Endpoint

HotRepo MCP server

No — it is up, but it requires credentials. HotRepo answered 2 days ago with an authentication challenge rather than a session.

Auth requiredLast checked 2 days ago

Server URL

https://hotrepo.ai/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
ai.hotrepo/hotrepo
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
GitHub Trending boards and AI-written reviews of trending open-source projects.
Listing
From the official MCP registry (active).
Recent checks of HotRepo
CheckedResultHandshake
2 days agoCredentials required—
6 days agoCredentials required—
16 days agoHandshake completed579 ms
17 days agoHandshake completed602 ms
18 days agoHandshake completed588 ms
19 days agoHandshake completed601 ms
21 days agoHandshake completed684 ms
21 days agoHandshake completed674 ms
22 days agoHandshake completed622 ms
23 days agoHandshake completed628 ms
25 days agoHandshake completed642 ms
28 days agoCredentials required—

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

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