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.
npx agentmods add mcp/arnavranjan005/mcp-telemetry/server-mcp-telemetry-servergit clone --depth 1 https://github.com/arnavranjan005/mcp-telemetryWrote 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/arnavranjan005/mcp-telemetry/server-mcp-telemetry-server)<a href="https://agentmods.dev/mcp/arnavranjan005/mcp-telemetry/server-mcp-telemetry-server"><img src="https://agentmods.dev/badge/mcp/arnavranjan005/mcp-telemetry/server-mcp-telemetry-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-telemetry-server 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 6d 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-telemetry-server": {
"command": "npx",
"args": [
"-y",
"mcp-telemetry-server"
],
"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.
- 6d ago First seen · 10 lines scan A 615b01055133
mcp-telemetry-server is an MCP server published in the GitHub repository arnavranjan005/mcp-telemetry (2 stars, last pushed 4d 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
21st
MCP server "21st", hosted remotely at 21st.dev, as configured in 21st-dev/magic-mcp.
subio-scrape
MCP server "subio-scrape" as configured in alijancb/subio-mcp. Runs locally from the @subio/mcp npm package.
papi
MCP server "papi", hosted remotely at mcp.getpapi.ai, as configured in getpapi/papi.
astravue
MCP server "astravue", hosted remotely at api.astravue.com, as configured in AstravueOrg/astravue-mcp-server.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.