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/yaniv-fink/wp-agent-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/yaniv-fink/wp-agent-mcp/wordpress)<a href="https://agentmods.dev/mcp/yaniv-fink/wp-agent-mcp/wordpress"><img src="https://agentmods.dev/badge/mcp/yaniv-fink/wp-agent-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/yaniv-fink/wp-agent-mcp/wordpress"><img src="https://agentmods.dev/badge/mcp/yaniv-fink/wp-agent-mcp/wordpress.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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
{
"wordpress": {
"url": "https://mcp.getwpagent.com/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A 1a5b7f46d458
wordpress is an MCP server published in the GitHub repository yaniv-fink/wp-agent-mcp (3 stars, last pushed 22d 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
slack-mcp-server
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth. Runs locally from the @jtalk22/slack-mcp npm package. Needs 2 environment variables to run.
tailscale-mcp
Tailscale MCP server for managing your tailnet from AI assistants. Runs locally from the @yawlabs/tailscale-mcp npm package.
a2asearch-mcp
Search 10,000+ AI agents, MCP servers, and CLI tools via A2ASearch from any MCP client. Runs locally from the a2asearch-mcp npm package.
papi
MCP server "papi", hosted remotely at mcp.getpapi.ai, as configured in getpapi/papi.
platfone
Virtual phone numbers for AI agents — rent numbers in 200+ countries, receive SMS. Runs locally from the @platfone/mcp npm package. Needs 1 environment variable to run.
mcp
Official GetXAPI MCP server — use the Twitter/X API (search, users, tweets, posting, DMs, articles) inside Claude, Cursor, and any MCP client. Runs locally from the @getxapi/mcp npm package.