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.
/plugin marketplace add antohins/seo-tools-mcpnpx agentmods add plugins/antohins/seo-tools-mcp/aparsergit clone --depth 1 https://github.com/antohins/seo-tools-mcpGrade A, and why
aparser 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 3d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "aparser",
"displayName": "SEO Tools: A-Parser bridge",
"version": "1.8.0",
"description": "Bridge to your own self-hosted A-Parser: SERP, suggests and 150+ parsers via its HTTP API. Read-only; needs your own A-Parser licence and server.",
"author": {
"name": "antohins",
"url": "https://github.com/antohins"
},
"homepage": "https://github.com/antohins/seo-tools-mcp/tree/main/servers/aparser#readme",
"repository": "https://github.com/antohins/seo-tools-mcp",
"license": "MIT",
"keywords": [
"seo",
"a-parser",
"aparser",
"serp",
"scraping",
"self-hosted"
],
"userConfig": {
"APARSER_URL": {
"type": "string",
"title": "A-Parser API endpoint",
"description": "Full URL including the path, e.g. http://IP:9091/API (A-Parser → Settings → API)."
},
"APARSER_PASSWORD": {
"type": "string",
"title": "A-Parser API password",
"description": "Password from the same settings page.",
"sensitive": true
}
}
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 145 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 36 lines scan A c886f91b70c0
aparser is a plugin published in the GitHub repository antohins/seo-tools-mcp (3 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
yandex-webmaster-mcp
MCP server for Yandex Webmaster — query indexing, search queries, diagnostics and backlinks, and recrawl URLs, in plain language. Secretless PKCE login, read-only by default, TypeScript.
spook
Spook SEO tools over MCP: analyze any domain for winnable queries, 45+ free SEO tools, and SEO article generation/publishing.
google-search-console-cli marketplace
Plugin marketplace listing 1 plugin: google-search-console-cli.
yandex-direct
Управление Яндекс.Директ: кампании, объявления, ставки, OAuth.
secedgar-mcp-server
Query SEC EDGAR filings, XBRL financials, and company data through MCP. STDIO & Streamable HTTP.
vault-pkm
Bidirectional knowledge flow between Claude Code and Obsidian — 20 MCP tools, skills, and hooks for PKM.