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/MarcSkovMadsen/holoviz-mcpWrote 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/marcskovmadsen/holoviz-mcp/holoviz)<a href="https://agentmods.dev/mcp/marcskovmadsen/holoviz-mcp/holoviz"><img src="https://agentmods.dev/badge/mcp/marcskovmadsen/holoviz-mcp/holoviz/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/marcskovmadsen/holoviz-mcp/holoviz"><img src="https://agentmods.dev/badge/mcp/marcskovmadsen/holoviz-mcp/holoviz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
holoviz 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 11d 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
{
"holoviz": {
"type": "stdio",
"command": ".pixi/envs/default/bin/holoviz-mcp",
"args": [],
"env": {}
}
}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.
- 11d ago First seen · 8 lines scan A 1089b2a7abb4
holoviz is an MCP server published in the GitHub repository MarcSkovMadsen/holoviz-mcp (34 stars, last pushed 10d ago), licensed BSD-3-Clause. 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-30.
Other mcp servers, from other repositories
dataviz-mcp
DataViz MCP is a local Panel web server that executes Python code snippets and renders the resulting visualizations as live, interactive web pages. Runs locally from the dataviz-mcp Python package.
dataloupe
MCP server "dataloupe" as configured in aurelio-nakamura/dataloupe. Runs in Docker (ghcr.io/aurelio-nakamura/dataloupe:0.13.0). Needs 1 environment variable to run.
microcharts
Find, wire, and render microcharts — word-sized React charts with generated alt text. Runs locally from the @microcharts/mcp npm package.
malloy
MCP server "malloy", hosted remotely at localhost, as configured in malloydata/publisher.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
supply-math
MCP server "supply-math" as configured in JiuTian-dev/SupplyChainCortex. Runs mcp-server/server.py with python.