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/dihannahdi/myceliumWrote 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/dihannahdi/mycelium/mycelium-datahub)<a href="https://agentmods.dev/mcp/dihannahdi/mycelium/mycelium-datahub"><img src="https://agentmods.dev/badge/mcp/dihannahdi/mycelium/mycelium-datahub/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/dihannahdi/mycelium/mycelium-datahub"><img src="https://agentmods.dev/badge/mcp/dihannahdi/mycelium/mycelium-datahub.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mycelium-datahub 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 9d 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
{ "mycelium-datahub": { "command": "uvx", "args": [ "mycelium-datahub" ] } }
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.
- 9d ago First seen · 8 lines scan A 78c5ed3ab3d3
mycelium-datahub is an MCP server published in the GitHub repository dihannahdi/mycelium (0 stars, last pushed 1mo 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-08-31.
Other mcp servers, from other repositories
praxis
MCP server "praxis" as configured in Marc-Dvci/praxis-datahub. Runs praxis.mcp with python. Needs 1 environment variable to run.
datahub
MCP server "datahub" as configured in Marc-Dvci/praxis-datahub. Runs locally from the mcp-server-datahub@latest Python package. Needs 2 environment variables to run.
datahub-polygraph
MCP server "datahub-polygraph" as configured in kishanraj41/datahub-polygraph. Runs locally from the datahub-polygraph Python package.
datahub-chaperone
MCP server "datahub-chaperone" as configured in praisejxy/datahub-chaperone. Runs locally from the datahub-chaperone Python package.
fadlie
MCP server "fadlie" as configured in benewende-dev/fadlie. Runs locally from the fadlie Python package.
ripplecheck
MCP server "ripplecheck" as configured in sohamkamat28/ripplecheck. Runs locally from the ripplecheck Python package.