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/musharna/data-aggregator-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/musharna/data-aggregator-mcp/data-aggregator)<a href="https://agentmods.dev/mcp/musharna/data-aggregator-mcp/data-aggregator"><img src="https://agentmods.dev/badge/mcp/musharna/data-aggregator-mcp/data-aggregator/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/musharna/data-aggregator-mcp/data-aggregator"><img src="https://agentmods.dev/badge/mcp/musharna/data-aggregator-mcp/data-aggregator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
data-aggregator 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
{
"data-aggregator": {
"command": "uvx",
"args": [
"data-aggregator-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 · 8 lines scan A 99a56530f026
data-aggregator is an MCP server published in the GitHub repository musharna/data-aggregator-mcp (4 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-31.
Other mcp servers, from other repositories
scigantic-mcp
MCP server for the Scigantic catalog of public scientific data archives, with LLM-ready schema cards. Runs locally from the scigantic-mcp Python package.
pubmed-mcp-server
Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms. Runs locally from the @cyanheads/pubmed-mcp-server npm package. Needs 4 environment variables to run.
uniprot-mcp-server
Protein research over UniProtKB — search by function, fetch curated records, map IDs, proteomes. Runs locally from the @cyanheads/uniprot-mcp-server npm package. Needs 1 environment variable to run.
mosaic-mcp
Pre-clinical drug discovery intelligence — 12 MCP tools for drug targets: profiles, compounds, patents, papers, structures, competitive landscape, pathways, validation, clinical pipeline, and synthetic-lethal whitespace. Runs locally from the mosaic-mcp Python package. Needs 3 environment variables to run.
plantcv
MCP server exposing PlantCV as a measurement instrument — traits plus the segmentation overlay they came from. Runs locally from the plantcv-mcp Python package.
plantcv-mcp
MCP server exposing PlantCV as a measurement instrument — traits plus the segmentation overlay they came from. Runs locally from the plantcv-mcp Python package.