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/leonardobora/mcp-wordpressWrote 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/leonardobora/mcp-wordpress/mcp-wordpress)<a href="https://agentmods.dev/mcp/leonardobora/mcp-wordpress/mcp-wordpress"><img src="https://agentmods.dev/badge/mcp/leonardobora/mcp-wordpress/mcp-wordpress/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/leonardobora/mcp-wordpress/mcp-wordpress"><img src="https://agentmods.dev/badge/mcp/leonardobora/mcp-wordpress/mcp-wordpress.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-wordpress 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
{ "mcp-wordpress": { "command": "npx", "args": [ "-y", "@leonardobora/mcp-wordpress" ] } }
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 · 9 lines scan A 52a00254f086
mcp-wordpress is an MCP server published in the GitHub repository leonardobora/mcp-wordpress (3 stars, last pushed 2mo 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
autotask-mcp
MCP server "autotask-mcp" as configured in WYRE-AI/autotask-mcp. Runs in Docker (ghcr.io/wyre-ai/autotask-mcp:v2.38.2). Needs 7 environment variables to run.
wordpress-mcp
Lightweight WordPress MCP server - 42 tools, token-optimized (95% smaller responses). Runs locally from the @cavort-it-systems/wordpress-mcp npm package. Needs 3 environment variables to run.
sprout-mcp-server
MCP server for Sprout Social API. Runs locally from the @oliverames/sprout-mcp-server npm package.
api-bridge
MCP server "api-bridge" as configured in AleBrito124356/mcp-server-cookbook. Runs C:\dev\mcp-server-cookbook\servers\api_bridge\dist\index.js with node.
hono-apcore
Hono adapter for the apcore AI-Perceivable module ecosystem. Runs locally from the hono-apcore npm package.
toolport-openapi-mcp
Turn any OpenAPI/Swagger spec into an MCP server: one tool per endpoint. A showcase for Toolport (toolport.app). Runs locally from the toolport-openapi-mcp npm package.