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/Data-Wise/craftWrote 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/data-wise/craft/mcp-mermaid)<a href="https://agentmods.dev/mcp/data-wise/craft/mcp-mermaid"><img src="https://agentmods.dev/badge/mcp/data-wise/craft/mcp-mermaid/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/data-wise/craft/mcp-mermaid"><img src="https://agentmods.dev/badge/mcp/data-wise/craft/mcp-mermaid.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
mcp-mermaid 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
{
"mcp-mermaid": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}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 Changed fa69927a87a6
- 1mo ago First seen · 9 lines scan A f9715d3f87f5
mcp-mermaid is an MCP server published in the GitHub repository Data-Wise/craft (4 stars, last pushed 6d 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
pharaoh
MCP proxy for Pharaoh — maps codebases into queryable knowledge graphs for AI agents. Enables Claude Code in headless environments (VPS, SSH, CI) via device flow auth. Runs locally from the @pharaoh-so/mcp npm package.
ai-software-architect
MCP server for AI Software Architect framework. Runs locally from the ai-software-architect npm package.
repo-cartographer
Maps any repo into an architecture diagram (Mermaid/Graphviz) and enforces architecture rules in CI. Runs locally from the repo-cartographer npm package.
azure-devops
MCP server for interacting with Azure DevOps. Runs locally from the @azure-devops/mcp npm package. Needs 3 environment variables to run.
knowbe4-mcp
MCP server "knowbe4-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/knowbe4-v0.1.3/knowbe4. Needs 4 environment variables to run.
rea
Reverse engineer anything from your terminal or agent with one CLI and MCP server. Runs locally from the rea-agents npm package.