reporadar-mcp.let-s-go-christo.workers.dev
https://reporadar-mcp.let-s-go-christo.workers.dev/mcp
active Production-safe Score 90/100 http no auth
At a glance
| Endpoint | https://reporadar-mcp.let-s-go-christo.workers.dev/mcp |
|---|---|
| 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:51:37 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 750 / 1258 ms |
| Last successful check | 2026-11-17 21:51:37 |
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:51:37 | ✓ | ✓ | 572 ms | 89 | active |
| 2026-11-17 21:36:28 | ✓ | ✓ | 714 ms | 89 | active |
| 2026-11-17 21:21:14 | ✓ | ✓ | 688 ms | 89 | active |
| 2026-11-17 21:06:06 | ✓ | ✓ | 705 ms | 89 | active |
| 2026-11-17 20:50:44 | ✓ | ✓ | 730 ms | 89 | active |
| 2026-11-17 20:35:40 | ✓ | ✓ | 959 ms | 89 | active |
| 2026-11-17 20:20:39 | ✓ | ✓ | 748 ms | 89 | active |
| 2026-11-17 20:05:38 | ✓ | ✓ | 679 ms | 89 | active |
| 2026-11-17 19:49:53 | ✓ | ✓ | 834 ms | 89 | active |
| 2026-11-17 19:34:46 | ✓ | ✓ | 979 ms | 89 | active |
| 2026-11-17 19:19:37 | ✓ | ✓ | 1106 ms | 86 | active |
| 2026-11-17 19:04:21 | ✓ | ✓ | 1108 ms | 86 | active |
| 2026-11-17 18:49:10 | ✓ | ✓ | 1026 ms | 86 | active |
| 2026-11-17 18:33:59 | ✓ | ✓ | 667 ms | 89 | active |
| 2026-11-17 18:18:51 | ✓ | ✓ | 682 ms | 89 | 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/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/reporadar-mcp-let-s-go-christo-workers-dev-mcp # JSON