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.
npx agentmods add mcp/bearlike/grove/grove-networkgit clone --depth 1 https://github.com/bearlike/GroveWrote 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/bearlike/grove/grove-network)<a href="https://agentmods.dev/mcp/bearlike/grove/grove-network"><img src="https://agentmods.dev/badge/mcp/bearlike/grove/grove-network.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
grove-network 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 3d 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
{
"grove-network": {
"type": "http",
"url": "http://host.docker.internal:7431/mcp",
"headers": {
"Authorization": "Bearer ${GROVE_MCP_TOKEN}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 8. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 9 lines scan A 1c3403815448
grove-network is an MCP server published in the GitHub repository bearlike/Grove (2 stars, last pushed 12d 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
agentkeeper-aria
MCP server "agentkeeper-aria" as configured in Thinklanceai/agentkeeper. Launched with agentkeeper-mcp --agent-id aria --provider anthropic. Needs 2 environment variables to run.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.
agent-tools
MCP server "agent-tools" as configured in RosuLaurentiu/ChainWhisper-MCP. Runs locally from the @chainwhisper/agent-tools npm package.
distillory
MCP server "distillory" as configured in everyai-com/distillory. Runs locally from the distillory Python package.
logic-server
Agent reasoning, memory, and token-optimized context for AI applications. Runs locally from the nocturnusai-mcp npm package. Needs 4 environment variables to run.
eudi-wallet-mcp
EUDI Wallet MCP — EU Digital Identity Wallet under eIDAS 2.0 for AI agent authentication. ISO 18013-5 (mDoc) + W3C VC 2.0 + OID4VC + OID4VP. By MEOK AI Labs. Runs locally from the eudi-wallet-mcp Python package.