reporadar-mcp.let-s-go-christo.workers.dev
https://reporadar-mcp.let-s-go-christo.workers.dev/sse
active Production-safe Score 90/100 http no auth
At a glance
| Endpoint | https://reporadar-mcp.let-s-go-christo.workers.dev/sse |
|---|---|
| Source | https://github.com/RepoRadar/reporadar/blob/main/workers/mcp/README.md |
| Transport | http |
| Tools | 2 |
| Auth | none |
| First seen | 2026-06-03 12:04:37 |
| Last checked | 2026-11-17 21:58:19 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 744 / 1303 ms |
| Last successful check | 2026-11-17 21:58:19 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (2)
rank_repos— Search GitHub via RepoRadar's curated multi-tier fallback (topic → keyword → all-time) and rank the results across 10 PRD dimensions: Momentdeploy_variant— Deploy a bespoke A2UI generative-UI micro-app for a specific GitHub repo. Pipes through RepoRadar's deploy worker, which asks Gemini to pick
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:58:19 | ✓ | ✓ | 975 ms | 89 | active |
| 2026-11-17 21:43:17 | ✓ | ✓ | 872 ms | 89 | active |
| 2026-11-17 21:28:16 | ✓ | ✓ | 1068 ms | 86 | active |
| 2026-11-17 21:13:08 | ✓ | ✓ | 699 ms | 89 | active |
| 2026-11-17 20:57:32 | ✓ | ✓ | 645 ms | 89 | active |
| 2026-11-17 20:42:31 | ✓ | ✓ | 958 ms | 89 | active |
| 2026-11-17 20:27:30 | ✓ | ✓ | 800 ms | 89 | active |
| 2026-11-17 20:12:29 | ✓ | ✓ | 1288 ms | 86 | active |
| 2026-11-17 19:55:11 | ✓ | ✓ | 1446 ms | 86 | active |
| 2026-11-17 19:40:04 | ✓ | ✓ | 1350 ms | 86 | active |
| 2026-11-17 19:24:45 | ✓ | ✓ | 1099 ms | 86 | active |
| 2026-11-17 19:09:38 | ✓ | ✓ | 712 ms | 90 | active |
| 2026-11-17 18:54:30 | ✓ | ✓ | 894 ms | 90 | active |
| 2026-11-17 18:39:23 | ✓ | ✓ | 879 ms | 90 | active |
| 2026-11-17 18:24:16 | ✓ | ✓ | 819 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://reporadar-mcp.let-s-go-christo.workers.dev/sse") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/reporadar-mcp-let-s-go-christo-workers-dev-sse # JSON