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 2mo 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.
- 2mo 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 3mo 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.
grok-agent-store compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| grok-agent-storemanhatton31-svg/grok-agent-store | MCP server | 1 | 3mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| eva_cli_exampletrpc-group/trpc-agent-go | MCP server | 1.9k | yesterday | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| cloudflare-apilouisbrulenaudet/monorepo-template | MCP server | 19 | 12d ago | Apache-2.0 | A | — | Cursor |
| mcp-serverWasmAgent/wasmagent-js | MCP server | 7 | today | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| marketplacekenwea-protocol/kenwea | MCP server | 2 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| notarykenwea-protocol/kenwea | MCP server | 2 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| grok-delegatezai-one/grok-build-mcp | MCP server | 2 | 29d ago | none | A | — | Claude Code |