HotRepo
connectsverified ownerhotrepo.ai
Discover open-source projects with GitHub Trending boards, AI-written reviews, topic search, history and monthly reports. Six read-only tools; free API key at hotrepo.ai/account.
https://hotrepo.ai/mcpWebsiteUnknownlast checked 26 Oct 2026spoke MCP on 1 of 1 check (30 days)initialize in 585 msLast checked 26 Oct 2026
- ✕Did not answer the MCP handshake
- –Auth scheme could not be determined
- ✕Lists no tools
- ✓No blockers or warnings
- ✓Spoke MCP on 1 of 1 check (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
–Claude CodeUnknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
Claude Code docs · read on 2026-08-30
–Claude (claude.ai & Desktop)Unknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
–ChatGPTUnknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
ChatGPT docs · read on 2026-08-30
–CursorUnknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
Cursor docs · read on 2026-08-30
–VS Code (Copilot)Unknown
The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.
VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 26 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | Unknown |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Refused — credentials required |
What the probe found
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Contract history
No contract recorded yet — the server has not answered an anonymous connection.
Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.
mcpi-cli publish https://hotrepo.ai/mcpGet alerted when this contract changes
Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Route it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayStatus badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/hotrepo)