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/NBNBTM/pddl-mcp-serverWrote 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/nbnbtm/pddl-mcp-server/pddl-planner)<a href="https://agentmods.dev/mcp/nbnbtm/pddl-mcp-server/pddl-planner"><img src="https://agentmods.dev/badge/mcp/nbnbtm/pddl-mcp-server/pddl-planner/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/nbnbtm/pddl-mcp-server/pddl-planner"><img src="https://agentmods.dev/badge/mcp/nbnbtm/pddl-mcp-server/pddl-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pddl-planner 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 9d 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.
This is a copy
86% identical to solidworks — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"pddl-planner": {
"command": "python",
"args": [
"server.py"
],
"cwd": "."
}
}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.
- 9d ago First seen · 9 lines scan A ac209051815c
pddl-planner is an MCP server published in the GitHub repository NBNBTM/pddl-mcp-server (5 stars, last pushed 8d 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. It is 86% identical to solidworks, differing in 5 lines, and is treated as a copy.
Other mcp servers, from other repositories
AynOps
A Model Context Protocol server that gives AI Clients real-time cybersecurity reconnaissance capabilities — WHOIS, DNS enumeration, port scanning, SSL inspection, CVE lookup, IP reputation, ASN lookup and more. Runs locally from the AynOps Python package. Needs 2 environment variables to run.
openroad-mcp
OpenROAD MCP server (TypeScript/npx). Runs locally from the openroad-mcp npm package.
sagemath
Model Context Protocol server that provides stateful SageMath computations. Runs locally from the sagemath-mcp Python package.
lucius-mcp
Allure TestOps MCP Server. Runs locally from the lucius-mcp Python package. Needs 3 environment variables to run.
osm-edit
Review-first MCP server for previewed, version-checked OpenStreetMap road edits from local GPX surveys. Runs locally from the osm-edit-mcp Python package. Needs 3 environment variables to run.
nexus-mcp
Model Context Protocol server for AI CLI agents. Runs locally from the nexus-mcp Python package.