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/ezbiz-services/mcp-seo-marketingWrote 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/ezbiz-services/mcp-seo-marketing/seo-marketing)<a href="https://agentmods.dev/mcp/ezbiz-services/mcp-seo-marketing/seo-marketing"><img src="https://agentmods.dev/badge/mcp/ezbiz-services/mcp-seo-marketing/seo-marketing/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/ezbiz-services/mcp-seo-marketing/seo-marketing"><img src="https://agentmods.dev/badge/mcp/ezbiz-services/mcp-seo-marketing/seo-marketing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
seo-marketing 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 11d 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
{
"seo-marketing": {
"url": "https://seo.ezbizservices.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.
- 11d ago First seen · 6 lines scan A eed36e88e581
seo-marketing is an MCP server published in the GitHub repository ezbiz-services/mcp-seo-marketing (0 stars, last pushed 6mo 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
Track keyword rankings, research SEO opportunities, and manage bisibility projects with AI agents. Runs locally from the @bisibility/mcp npm package. Needs 5 environment variables to run.
yg3-mcp
Marketing MCP: content, SEO, outbound, LinkedIn, ads. Agents provision a sandbox with one POST. Remote server at mcp.yg3.ai.
seo-audit
Free SEO & AI-search (AEO) audits for any site or Shopify store, with emailed weekly score reports. Remote server at inxy.ai.
theseo-mcp
MCP server "theseo-mcp", hosted remotely at theseo-mcp.sales-cc8.workers.dev, as configured in GianlucaNaarden/theseo-mcp.
spook
MCP server "spook", hosted remotely at www.tryspook.com, as configured in VictorKildahl/spook-mcp.
influship-mcp
Find and analyze influencers with creator search, lookalikes, profiles, posts, and transcripts. Runs locally from the @influship/mcp npm package. Needs 2 environment variables to run.