grokbot.tools
REMOTE · MCP.GROKBOT.TOOLS
Search Grok Bot connectors, install methods, test status, and the connector wishlist.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1309 tokens (~218/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://mcp.grokbot.tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=grokbot.tools | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | db052ecc27670ab30e394ed9ec691f2d |
| SANs: grokbot.tools, mcp.grokbot.tools, *.mcp.grokbot.tools | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.grokbot.tools. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | present | 13831 | 8 | Verified |
| grokbot.tools. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.grokbot.tools/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.grokbot.tools/mcp | HTTPS enforced | 301 | https://mcp.grokbot.tools/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_connector Get one Grok Bot connector ~139
Get the full public record for one published connector by its slug (the last part of https://grokbot.tools/connectors/{slug}): summary, install method with step-by-step instructions and sources, MCP URL (null for built-in plugins), auth type, docs link, Grok Bot test status with the last test date, notes, related wishlist requests, and the page URL. Status is never 'Verified' unless it was verified inside Grok Bot with a dated test. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Connector slug, e.g. 'notion', 'linear', 'context7'. Find slugs with search_connectors. |
No output schema declared.
No examples provided.
get_request Get one wishlist request ~119
Get one wishlist request by slug (the last part of https://grokbot.tools/requests/{slug}): status, on-site votes, the labeled seed signal, description, public sources (links to the posts it came from), the linked connector if one exists, the builder if it has been claimed, and a matching setup guide when there is one. Slugs of requests that were merged resolve to the surviving request. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Request slug, e.g. 'whatsapp'. Find slugs with list_requests. |
No output schema declared.
No examples provided.
how_to_add_connector How to add a connector to Grok Bot ~87
Explains how an app gets into Grok Bot: built-in plugins (Connect apps in the sidebar), custom MCP servers (you ask the Bot in chat to add a URL; must be public HTTPS using streamable HTTP or SSE), and the browser-only route when neither exists. Includes this server's own URL as a worked example. Takes no input and reads nothing from the database.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_connectors List Grok Bot connectors ~347
Page through every published connector in the grokbot.tools directory, alphabetically, with the same optional filters as search_connectors. Returns compact summaries plus the total, the categories in use (first page), and a next_cursor to pass back for the next page. Use this when you want the whole directory; use search_connectors when you know what you are looking for. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_type | string | – | 'oauth' = you sign in with your own account; 'public' = no sign-in. |
| category | string | – | Exact category name, case-insensitive, e.g. 'Developer tools & data', 'Money', 'Design', 'Docs & search', 'Projects & docs', 'Sales & support', 'Files', 'Security'. Use list_connectors with no filter… |
| cursor | string | – | Opaque cursor from a previous result's next_cursor. Omit for the first page. |
| install_method | string | – | How the app gets into Grok Bot: built-in plugin (Connect apps), custom MCP URL added via chat, browser only, or unverified. |
| limit | integer | – | Page size, 1-50 (default 20). Larger values are clamped to 50. |
| query | string | – | Optional free-text filter on name, service, category and slug. |
| status | string | – | Grok Bot test status. 'verified' = dated test inside Grok Bot. 'seen_working' = seen working, dated re-test pending. 'unknown' = not re-tested inside Grok Bot yet (includes seen_working). 'broken' =… |
No output schema declared.
No examples provided.
list_requests List the connector wishlist ~182
List the grokbot.tools wishlist: apps people want connected to Grok Bot, sorted by on-site votes or by newest. Each item has its status (requested, claimed, live), on-site vote count, the labeled seed signal ('X buzz (seed)', mentions elsewhere that are never counted as votes), a linked connector if one exists, and its page URL. Votes are only votes made on grokbot.tools and start at 0. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, 1-25 (default 10). Larger values are clamped to 25. |
| sort | string | – | 'votes' = most on-site votes first, then seed buzz (default). 'recent' = newest first. |
| status | string | – | Only requests in this state. 'live' means a connector exists. Omit for all. |
No output schema declared.
No examples provided.
search_connectors Search Grok Bot connectors ~350
Search the grokbot.tools directory of MCP connectors and plugins for Grok Bot by name, service or category, with optional filters (Grok Bot test status, install method, auth type). Returns compact summaries with the install method, auth type, honest test-status label and the grokbot.tools page URL; use get_connector for install steps and the MCP URL. Only published directory entries are returned. Read-only; independent fan project, not affiliated with xAI.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_type | string | – | 'oauth' = you sign in with your own account; 'public' = no sign-in. |
| category | string | – | Exact category name, case-insensitive, e.g. 'Developer tools & data', 'Money', 'Design', 'Docs & search', 'Projects & docs', 'Sales & support', 'Files', 'Security'. Use list_connectors with no filter… |
| install_method | string | – | How the app gets into Grok Bot: built-in plugin (Connect apps), custom MCP URL added via chat, browser only, or unverified. |
| limit | integer | – | Max results, 1-25 (default 10). Larger values are clamped to 25. |
| query | string | – | Free text matched against connector name, service, category and slug, e.g. 'notion' or 'payments'. |
| status | string | – | Grok Bot test status. 'verified' = dated test inside Grok Bot. 'seen_working' = seen working, dated re-test pending. 'unknown' = not re-tested inside Grok Bot yet (includes seen_working). 'broken' =… |
No output schema declared.
No examples provided.
How do I install the grokbot.tools MCP server?
grokbot.tools is a hosted endpoint at https://mcp.grokbot.tools/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.grokbot.tools
claude mcp add --transport http tools-grokbot-connectors 'https://mcp.grokbot.tools/mcp'
What is the grokbot.tools MCP server?
grokbot.tools is an MCP server listed in the public MCP registry as tools.grokbot/connectors. Search Grok Bot connectors, install methods, test status, and the connector wishlist. This page covers its hosted endpoint (https://mcp.grokbot.tools/mcp).
Is the grokbot.tools MCP server safe to use?
grokbot.tools scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the grokbot.tools MCP server expose?
grokbot.tools exposes 6 tools: search_connectors, get_connector, list_connectors, list_requests, get_request, how_to_add_connector. Their descriptions and schemas cost roughly 1,224 tokens of context every time the server is loaded.
Does the grokbot.tools MCP server require authentication?
No. We connected to grokbot.tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the grokbot.tools MCP server still maintained?
grokbot.tools is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.