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/MVPR-Ext-Projects/planday-bridgeWrote 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/mvpr-ext-projects/planday-bridge/planday)<a href="https://agentmods.dev/mcp/mvpr-ext-projects/planday-bridge/planday"><img src="https://agentmods.dev/badge/mcp/mvpr-ext-projects/planday-bridge/planday/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/mvpr-ext-projects/planday-bridge/planday"><img src="https://agentmods.dev/badge/mcp/mvpr-ext-projects/planday-bridge/planday.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
planday 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
{
"planday": {
"command": "pnpm",
"args": [
"tsx",
"apps/mcp/index.ts"
],
"cwd": ".",
"env": {
"PLANDAY_MODE": "dummy",
"PLANDAY_WRITE_TIER": "read"
}
}
}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 · 14 lines scan A b3f0788dbf6f
planday is an MCP server published in the GitHub repository MVPR-Ext-Projects/planday-bridge (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
monday
MCP server "monday", hosted remotely at mcp.monday.com, as configured in mondaycom/mcp.
mcp-server
Hosted OAuth MCP at https://www.taskade.com/mcp, or local @taskade/mcp-server. Runs locally from the @taskade/mcp-server npm package. Needs 1 environment variable to run.
pipefy
MCP server "pipefy", hosted remotely at mcp.pipefy.com, as configured in pipefy/ai-toolkit.
office-oxide-mcp
Rust-native MCP server for Office document processing. Runs locally from the @aimino/opendocswork-mcp npm package.
p4plan-mcp
MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API. Runs locally from the @perforce/p4plan-mcp npm package. Needs 3 environment variables to run.
openproject-mcp-server
MCP server for OpenProject: 89 tools for work packages, attachments, git activity, time tracking, meetings and reporting over the API v3. Runs locally from the openproject-mcp-server Python package. Needs 5 environment variables to run.