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/megaplan-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/megaplan-mcp/megaplan)<a href="https://agentmods.dev/mcp/theyahia/megaplan-mcp/megaplan"><img src="https://agentmods.dev/badge/mcp/theyahia/megaplan-mcp/megaplan/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/theyahia/megaplan-mcp/megaplan"><img src="https://agentmods.dev/badge/mcp/theyahia/megaplan-mcp/megaplan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
megaplan 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
{
"megaplan": {
"command": "npx",
"args": [
"-y",
"@theyahia/megaplan-mcp"
],
"env": {
"MEGAPLAN_DOMAIN": "",
"MEGAPLAN_TOKEN": ""
}
}
}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 · 13 lines scan A 252daa649cc9
megaplan is an MCP server published in the GitHub repository theYahia/megaplan-mcp (2 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
planfix
MCP server for Planfix — tasks, contacts, project management (Russia). Runs locally from the @theyahia/planfix-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.
microsoft-planner-mcp
MCP server "microsoft-planner-mcp", hosted remotely at localhost, as configured in aixolotl/microsoft-planner-mcp.
mcp-server
Project portfolio management for PMOs. Alternative to Microsoft Project Online. OAuth + PAT. Remote server at mcp.onplana.com.
weeek-mcp-smart
WEEEK tasks by name, not IDs — an MCP server. Runs locally from the weeek-mcp-smart npm package. Needs 5 environment variables to run.
tilda
MCP server for Tilda — website builder, page management (Russia). Runs locally from the @theyahia/tilda-mcp npm package. Needs 2 environment variables to run.