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/malloydata/publisherWrote 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/malloydata/publisher/malloy)<a href="https://agentmods.dev/mcp/malloydata/publisher/malloy"><img src="https://agentmods.dev/badge/mcp/malloydata/publisher/malloy/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/malloydata/publisher/malloy"><img src="https://agentmods.dev/badge/mcp/malloydata/publisher/malloy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
malloy 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
{
"malloy": {
"type": "http",
"url": "http://localhost:4040/mcp"
}
}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 424aaa6e82b2
malloy is an MCP server published in the GitHub repository malloydata/publisher (118 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
lightdash-docs
MCP server "lightdash-docs", hosted remotely at docs.lightdash.com, as configured in lightdash/lightdash.
sentry
Sentry's hosted MCP server: lets the agent search and read issues, errors and traces. Remote server at mcp.sentry.dev.
tableau-lineage
Local-only Tableau .twbx audit: lineage, unused fields, duplicate calcs, SQL, version diffs. Runs locally from the tableau-lineage-mcp npm package.
lineage
Tableau workbook lineage and audit MCP server. Runs 100% locally, the .twbx never leaves your machine. Calculated-field lineage, unused fields, duplicate calcs, performance findings, version diffs, stored SQL. Runs locally from the tableau-lineage-mcp npm package.
scala-score
MCP server for S.C.A.L.A. Score API — let Claude, ChatGPT, and AI agents search 250M+ companies. Runs locally from the scala-mcp-server npm package. Needs 1 environment variable to run.