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/avansaber/seo-monsterWrote 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/avansaber/seo-monster/seomonster)<a href="https://agentmods.dev/mcp/avansaber/seo-monster/seomonster"><img src="https://agentmods.dev/badge/mcp/avansaber/seo-monster/seomonster/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/avansaber/seo-monster/seomonster"><img src="https://agentmods.dev/badge/mcp/avansaber/seo-monster/seomonster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
seomonster 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.
What it actually says
{
"seomonster": {
"command": "uvx",
"args": [
"seo-monster"
],
"env": {
"SEO_MCP_GOOGLE_OAUTH_CLIENT": "${SEO_MCP_GOOGLE_OAUTH_CLIENT}",
"SEO_MCP_GOOGLE_TOKEN": "${SEO_MCP_GOOGLE_TOKEN}",
"SEO_MCP_GSC_DEFAULT_SITE": "${SEO_MCP_GSC_DEFAULT_SITE}",
"SEO_MCP_GA4_PROPERTY_ID": "${SEO_MCP_GA4_PROPERTY_ID}",
"PSI_API_KEY": "${PSI_API_KEY}",
"CF_API_TOKEN": "${CF_API_TOKEN}",
"CF_ZONE": "${CF_ZONE}",
"SEO_MCP_INDEXNOW_KEY": "${SEO_MCP_INDEXNOW_KEY}",
"SEO_MCP_INDEXNOW_KEY_LOCATION": "${SEO_MCP_INDEXNOW_KEY_LOCATION}"
}
}
}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 · 19 lines scan A 821beead1191
seomonster is an MCP server published in the GitHub repository avansaber/seo-monster (157 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. 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
mcp-trustlayer
MCP server "mcp-trustlayer" as configured in neelbarm/mcp-trustlayer. Runs locally from the mcp-trustlayer Python package.
memocall
Recall past Claude Code conversations from any project as clean, compact Markdown. Runs locally from the memocall npm package.
tracer
MCP server "tracer" as configured in aiquilibria/contAIned. Runs contained.tracer_mcp with python3.
sn-patterns-mcp
ServiceNow Discovery pattern intelligence MCP server — Python NDL parser/writer + 28 MCP tools (read, search, validate, author, surgical-edit, emulate). Runs locally from the sn-patterns-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.