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/manhatton31-svg/grok-agent-storeWrote 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/manhatton31-svg/grok-agent-store/grok-agent-store)<a href="https://agentmods.dev/mcp/manhatton31-svg/grok-agent-store/grok-agent-store"><img src="https://agentmods.dev/badge/mcp/manhatton31-svg/grok-agent-store/grok-agent-store/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/manhatton31-svg/grok-agent-store/grok-agent-store"><img src="https://agentmods.dev/badge/mcp/manhatton31-svg/grok-agent-store/grok-agent-store.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grok-agent-store 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 11d 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-agent-store": {
"url": "https://grok-agent-store.manhatton31.workers.dev/mcp",
"type": "streamable-http"
}
}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.
- 11d ago First seen · 6 lines scan A 353516739962
grok-agent-store is an MCP server published in the GitHub repository manhatton31-svg/grok-agent-store (1 stars, last pushed 1mo 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
eva_cli_example
MCP server "evacliexample" as configured in trpc-group/trpc-agent-go. Launched with go run ./mcpserver.
mcp-server
WasmAgent MCP server — WASM-sandboxed code execution with capability manifests and Tasks API. Runs locally from the @wasmagent/mcp-server npm package.
grok-delegate
MCP server "grok-delegate" as configured in zai-one/grok-build-mcp. Launched with ${GROK_MCP_PYTHON:-py} -c import os, sys; sys.path.insert(0, os.environ.get('CLA. Needs 2 environment variables to run.
auth-token-service
Hash passwords with bcrypt and issue/verify JWT session tokens over A2A + MCP. Remote server at bcrypt-python-jose-d0e0d0.getvda.ai.
authenticated-llm-agent
JWT-gated LLM gateway: authenticate (bcrypt/JWT), then run a LangChain-on-Vertex Gemini completion. Remote server at bcrypt-langchain-openai-mcp-bb738e.getvda.ai.
llm-observability-orchestration
Run a prompt through a LangChain (system + human) chain over Gemini on Vertex AI; optional LangSmith. Remote server at langchain-core-langsmith-openai-8c02f9.getvda.ai.