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/richardwilkinson9/statlyte-dataWrote 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/richardwilkinson9/statlyte-data/statlyte)<a href="https://agentmods.dev/mcp/richardwilkinson9/statlyte-data/statlyte"><img src="https://agentmods.dev/badge/mcp/richardwilkinson9/statlyte-data/statlyte/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/richardwilkinson9/statlyte-data/statlyte"><img src="https://agentmods.dev/badge/mcp/richardwilkinson9/statlyte-data/statlyte.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
statlyte 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
{
"statlyte": {
"command": "npx",
"args": [
"-y",
"statlyte"
],
"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.
- 1mo ago First seen · 10 lines scan A 33311f1b84ee
statlyte is an MCP server published in the GitHub repository richardwilkinson9/statlyte-data (0 stars, last pushed 2mo 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
promptspend
LLM pricing where every rate carries its source and the date it was last confirmed. Runs locally from the @promptspend/mcp npm package.
llm-latency-tracker
Measured latency, time to first token and uptime for 45 AI inference APIs, by region. Remote server at llmlatency.dev.
vox-mcp
Multi-model AI gateway for MCP clients — routes prompts to Gemini, OpenAI, Anthropic, xAI, DeepSeek, Moonshot, OpenRouter, Cloudflare AI Gateway, Vercel AI Gateway, and local models with conversation memory. Runs locally from the vox-mcp Python package. Needs 19 environment variables to run.
distil
Compression with a quality contract — cache-aware, causally-pruned context compression for agentic runtimes, gated by a statistical non-inferiority test. Runs locally from the distil-llm Python package.
mutual-review
MCP server that runs mutual code review using Claude and GPT-4o, then synthesizes the findings. Runs locally from the mutual-review-mcp Python package. Needs 5 environment variables to run.
prolog-reasoner
LLM-powered logical reasoning with Prolog - Calculator for logic. Runs locally from the prolog-reasoner Python package.