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/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/huggingface)<a href="https://agentmods.dev/mcp/bearlike/grove/huggingface"><img src="https://agentmods.dev/badge/mcp/bearlike/grove/huggingface/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/bearlike/grove/huggingface"><img src="https://agentmods.dev/badge/mcp/bearlike/grove/huggingface.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
huggingface 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 1mo 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
{
"huggingface": {
"type": "http",
"url": "https://hf.co/mcp"
}
}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.
- 1mo ago First seen · 6 lines scan A 55326a5594b7
huggingface is an MCP server published in the GitHub repository bearlike/Grove (9 stars, last pushed 17d 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
vendo
MCP server "vendo", hosted remotely, as configured in runvendo/vendo.
data-workers
Data Workers CLI — autonomous AI agent swarm for data engineering. Runs locally from the dw-claw npm package.
thinking-prompts
MCP server "thinking-prompts" as configured in zdrjson/thinking-prompts-skill. Runs locally from the thinking-prompts npm package.
chroma_db_rag
MCP server "chromadbrag" as configured in laxmimerit/MCP-Mastery-with-Claude-and-Langchain. Launched with uv --directory D:\Courses\Udemy\MCP Mastery - Claude and LangChain\08 MCP RAG wi.
research-assistant
A Model Context Protocol server for research assistance with ChromaDB vector storage. Runs locally from the research-assistant-mcp Python package. Needs 2 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.