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/theYahia/planfix-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/theyahia/planfix-mcp/planfix)<a href="https://agentmods.dev/mcp/theyahia/planfix-mcp/planfix"><img src="https://agentmods.dev/badge/mcp/theyahia/planfix-mcp/planfix.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
planfix 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
{
"planfix": {
"command": "npx",
"args": [
"-y",
"@theyahia/planfix-mcp"
],
"env": {
"PLANFIX_API_KEY": "",
"PLANFIX_ACCOUNT": ""
}
}
}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 · 13 lines scan A 54a0ff9c7564
planfix is an MCP server published in the GitHub repository theYahia/planfix-mcp (3 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
moysklad
MCP server for MoySklad — warehouse, inventory, orders, reports (Russia). Runs locally from the @theyahia/moysklad-mcp npm package. Needs 1 environment variable to run.
megaplan
MCP server for Megaplan — tasks, deals, project management (Russia). Runs locally from the @theyahia/megaplan-mcp npm package. Needs 2 environment variables to run.
kaiten
MCP server for Kaiten — kanban boards, cards, spaces, checklists, project management (Russia). Runs locally from the @theyahia/kaiten-mcp npm package. Needs 3 environment variables to run.
moysklad-mcp
MCP server for MoySklad — warehouse, inventory, orders, reports (Russia). Runs locally from the @theyahia/moysklad-mcp npm package.
yandex-direct
MCP server for Yandex Direct — 20 tools: PPC campaigns, ad groups, ads, keywords, bids, negative keywords, statistics, balance (Russia). Rubles I/O, sandbox support. Runs locally from the @theyahia/yandex-direct-mcp npm package. Needs 1 environment variable to run.
yandex-direct-mcp
MCP server for Yandex Direct — PPC campaigns, ads, keywords, statistics (Russia). Runs locally from the @theyahia/yandex-direct-mcp npm package.