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.
npx agentmods add mcp/varaprasadreddy9676/openproject-codex-plugin/openproject-codex-openproject_codexgit clone --depth 1 https://github.com/varaprasadreddy9676/openproject-codex-pluginWrote 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/varaprasadreddy9676/openproject-codex-plugin/openproject-codex-openproject_codex)<a href="https://agentmods.dev/mcp/varaprasadreddy9676/openproject-codex-plugin/openproject-codex-openproject_codex"><img src="https://agentmods.dev/badge/mcp/varaprasadreddy9676/openproject-codex-plugin/openproject-codex-openproject_codex.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
openproject_codex 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 2d 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
{
"openproject_codex": {
"command": "python3",
"args": [
"./scripts/run_openproject_mcp.py"
],
"cwd": ".",
"env": {
"OPENPROJECT_BASE_URL": "https://your-openproject.example.com",
"OPENPROJECT_DEFAULT_PROJECT": "",
"OPENPROJECT_API_TOKEN_FILE": "~/.codex/secrets/openproject-api-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.
- 2d ago First seen · 14 lines scan A f3856f15fc96
openproject_codex is an MCP server published in the GitHub repository varaprasadreddy9676/openproject-codex-plugin (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
mindtrain
MCP server "mindtrain" as configured in shigella520/MindTrain. Runs ./scripts/mindtrain_mcp_bridge.py with python3.
openproject-mcp-server
MCP server for OpenProject: 87 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.
codex-win-to-wsl
MCP server "codex-win-to-wsl" as configured in Yuyu123fish/codex-win-to-wsl. Runs ./mcp/server.mjs with node.
openproject
Manage OpenProject projects, work packages, files, relations, boards, users, and notifications. Runs locally from the openproject-codex-plugin npm package. Needs 6 environment variables to run.
openproject
MCP server "openproject" as configured in alex13slem/openproject-codex-plugin. Launched with bun scripts/server.ts.
memi
Memi is the design layer for agentic AI. Runs locally from the @memi-design/cli npm package.