grok-mcp-server
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y grok-mcp-server@0.2.4
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
x_search prompt, instructions, previous_response_id, output_schema, model
Search X (formerly Twitter) in real-time using Grok's X Search. Supports structured output via JSON Schema and multi-turn chaining via response IDs. Use this tool when you need: - Real-time posts, trends, or public opinion from X - Fetching a specific post and its thread/replies by URL - Structured extraction of X data (topics, sentiment, reactions, etc.) - Follow-up searches that build on a previous result (drill-down, filtering, summarization) Workflow for deep research: 1. First call: use output_schema to get structured data + capture response_id 2. Follow-up calls: pass previous_response_id to continue with context Workflow for thread extraction: 1. Pass the post URL as prompt with output_schema to get structured thread data (original post + top replies ranked by engagement) 2. Use the returned structured data for analysis, commentary, or conversation
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | not stated |
| Source | github.com/valda/grok-mcp-server |
| Install scripts | sharp declare them. This runner does not run them. |
| Tarball | sha512-43n2XC8uf8x2TUx94q4//OgD9K6SrjV2a1K1/3xgNXAr9UR/7BHPcOBGsjJu879r67KUKwRkQZxZa+O6h0V8hw== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/grok-mcp-server)
New version out? Ask for a fresh report.