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/unitedideas/actablesite-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/unitedideas/actablesite-mcp/readiness)<a href="https://agentmods.dev/mcp/unitedideas/actablesite-mcp/readiness"><img src="https://agentmods.dev/badge/mcp/unitedideas/actablesite-mcp/readiness.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
readiness 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 7d 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
{
"readiness": {
"url": "https://actablesite.com/mcp",
"type": "streamable-http"
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 7d ago First seen · 6 lines scan A 3444c572ff40
readiness is an MCP server published in the GitHub repository unitedideas/actablesite-mcp (0 stars, last pushed 1mo 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
cargo
Structured Rust cargo operations (build, test, clippy) as typed JSON. Runs locally from the @paretools/cargo npm package.
docker
Structured Docker operations (ps, images, logs, build) as typed JSON. Runs locally from the @paretools/docker npm package.
http
MCP server for HTTP requests (curl) with structured, token-efficient output. Runs locally from the @paretools/http npm package.
lint
Structured linting output (ESLint, format-check) as typed JSON diagnostics. Runs locally from the @paretools/lint npm package.
make
MCP server for Make/Just task runners with structured, token-efficient output. Runs locally from the @paretools/make npm package.
pare-git
Pare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON. Runs locally from the @paretools/git npm package.