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/VasiHemanth/grok-build-pluginWrote 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/vasihemanth/grok-build-plugin/grok)<a href="https://agentmods.dev/mcp/vasihemanth/grok-build-plugin/grok"><img src="https://agentmods.dev/badge/mcp/vasihemanth/grok-build-plugin/grok/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/vasihemanth/grok-build-plugin/grok"><img src="https://agentmods.dev/badge/mcp/vasihemanth/grok-build-plugin/grok.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
Grade A, and why
grok 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 26d 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.
What it actually says
{
"grok": {
"command": "npx",
"args": [
"-y",
"grok-build-x-search-mcp"
]
}
}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.
- 26d ago First seen · 9 lines scan A 7785a093cb21
grok is an MCP server published in the GitHub repository VasiHemanth/grok-build-plugin (30 stars, last pushed 26d ago), licensed Apache-2.0. 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-09-20.
Other mcp servers, from other repositories
search-boost
Multi-engine web search for coding agents — one SearchBoost core (fused search, fetch, X) with MCP (Cursor, Codex, Claude Code, Grok Build, Antigravity), pi extension, and DeepSeek Harness bundle adapters. Runs locally from the search-boost npm package.
ai-consensus-mcp
Stdio MCP server exposing the Consensus Validation Protocol as a single consensus tool. Thin wrapper over ai-consensus-core. Runs locally from the ai-consensus-mcp npm package. Needs 5 environment variables to run.
mako-ai
Agentmako is a local project intelligence CLI and MCP server for codebases and databases, with repo-aware indexing, schema snapshots, and secure live database connectivity. Runs locally from the agentmako npm package.
grok-subagent
MCP server "grok-subagent" as configured in Walvez/grok-subagent. Runs ./mcp-server/server.mjs with node.
mcp-oauth-connect
Ping-only MCP origin for claude.ai, Desktop, Cursor, and Grok Connectors. Remote server at mcp.gfbytes.com.
alchemy
Serves the Alchemy writing ruleset to any agent, so its prose loses the usual LLM tells. Runs locally from the @fernforge/alchemy-mcp npm package.