Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/wousp112/grok2api-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/wousp112/grok2api-mcp-server/grok-mcp-server)<a href="https://agentmods.dev/mcp/wousp112/grok2api-mcp-server/grok-mcp-server"><img src="https://agentmods.dev/badge/mcp/wousp112/grok2api-mcp-server/grok-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/wousp112/grok2api-mcp-server/grok-mcp-server"><img src="https://agentmods.dev/badge/mcp/wousp112/grok2api-mcp-server/grok-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grok-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- grok-mcp-server — 100% identical, 0 lines differ
What it actually says
{ "grok-mcp-server": { "command": "npx", "args": [ "-y", "grok-mcp-server" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 9 lines scan A de806e7381af
grok-mcp-server is an MCP server published in the GitHub repository wousp112/grok2api-mcp-server (4 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
servicenow
MCP server "servicenow" as configured in serac-labs/serac. Runs locally from the servicenow-mcp-stdio npm package.
state-memory-mcp
Deterministic, persistent graph server for tracking workflow state, decisions, and blockers. Runs locally from the @putervision/state-memory-mcp npm package.
vynix-mcp
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis. Runs locally from the @usevynix/mcp-server npm package. Needs 2 environment variables to run.
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.
mcp-producer
MCP Server for Producer AI Music Generation via AceDataCloud API. Runs locally from the mcp-producer Python package. Needs 1 environment variable to run.
todox
Memory for coding agents: the decisions, the dead ends, and where the last session stopped. Remote server at www.todox.dev.