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/CynaCons/PowerScrollInstalling this writes the configuration, not the program: `python` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/cynacons/powerscroll/powerplan)<a href="https://agentmods.dev/mcp/cynacons/powerscroll/powerplan"><img src="https://agentmods.dev/badge/mcp/cynacons/powerscroll/powerplan/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/cynacons/powerscroll/powerplan"><img src="https://agentmods.dev/badge/mcp/cynacons/powerscroll/powerplan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
powerplan 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
{
"powerplan": {
"command": "python",
"args": [
"powerplan/powerplan_server.py"
],
"env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUNBUFFERED": "1"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 1mo ago First seen · 12 lines scan A fc8d5c504a4c
powerplan is an MCP server published in the GitHub repository CynaCons/PowerScroll (0 stars, last pushed 2d 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
expo
MCP server "expo", hosted remotely at mcp.expo.dev, as configured in fastrepl/anarlog.
mcp
Model Context Protocol server for Citadel: encrypted memory as MCP tools. Runs locally from the citadeldb-mcp Python package. Needs 1 environment variable to run.
lightworker
MCP server "lightworker" as configured in ncepuee/LightWorker. Runs locally from the lightworker Python package.
agent-bridge
First-party local TaskTime Pro tools for tasks, timers, expenses, invoices, reports, and planning. Runs locally from the @tasktimepro/agent-bridge npm package.
shutter-mcp
MCP server "shutter-mcp" as configured in keivanmalhani/shutter-mcp. Runs locally from the shutter-mcp Python package.
trip
A locally running MCP server for searching accommodation, flights, and tourist attractions, plus managing structured travel activities. It provides 20 tools and needs three environment variables to run.