grokbot.zone
https://grokbot.zone/mcp
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://grokbot.zone/mcp |
|---|---|
| Source | https://github.com/shagghiesuperstar/grokbotzoneMCP/blob/main/.mcp.json |
| Transport | http |
| Tools | 9 |
| Auth | none |
| First seen | 2026-11-10 15:52:21 |
| Last checked | 2026-11-17 21:46:56 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 295 / 1691 ms |
| Last successful check | 2026-11-17 21:46:56 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (9)
grokbot_check_listed— Reports whether a Grok bot code is already in the directory. Pass a link or a code.grokbot_get_bot— Returns the public record for one bot id.grokbot_get_category— Returns the bots filed under one category slug.grokbot_health— Reports whether the directory API and its database are up.grokbot_list_categories— Returns every category slug, label, count and purpose.grokbot_search— Scores public listings by how many query words appear in the name and description. Name matches count double. Optionally filter to one authogrokbot_submit_bot— Queues a public Grok bot for listing and sends a receipt to the given email. Uses the same checks and rate limit as the submit form.grokbot_subscribe— Starts a double opt-in for twice-weekly update emails. Nothing is sent until the confirm link is clicked. Uses the same rate limit as the sugrokbot_trending— Returns bot ids in trending order, optionally for one category.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:46:56 | ✓ | ✓ | 399 ms | 91 | active |
| 2026-11-17 21:31:51 | ✓ | ✓ | 312 ms | 91 | active |
| 2026-11-17 21:16:42 | ✓ | ✓ | 337 ms | 91 | active |
| 2026-11-17 21:01:39 | ✓ | ✓ | 340 ms | 91 | active |
| 2026-11-17 20:46:17 | ✓ | ✓ | 199 ms | 94 | active |
| 2026-11-17 20:31:15 | ✓ | ✓ | 414 ms | 91 | active |
| 2026-11-17 20:16:08 | ✓ | ✓ | 261 ms | 94 | active |
| 2026-11-17 20:00:13 | ✓ | ✓ | 334 ms | 91 | active |
| 2026-11-17 19:45:09 | ✓ | ✓ | 332 ms | 91 | active |
| 2026-11-17 19:29:53 | ✓ | ✓ | 359 ms | 91 | active |
| 2026-11-17 19:14:51 | ✓ | ✓ | 350 ms | 91 | active |
| 2026-11-17 18:59:05 | ✓ | ✓ | 363 ms | 91 | active |
| 2026-11-17 18:44:03 | ✓ | ✓ | 298 ms | 94 | active |
| 2026-11-17 18:29:02 | ✓ | ✓ | 478 ms | 91 | active |
| 2026-11-17 18:14:01 | ✓ | ✓ | 452 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://grokbot.zone/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/grokbot-zone-mcp # JSON