agentmods.dev

seo-tools-mcp-xmlriver

seo-tools-mcp-xmlriver is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from antohins/seo-tools-mcp. Its token cost is not measured, scanned A, original, MIT.

A read-only tool for checking Google and Yandex search results, image and news results, and whether URLs are indexed, using the XMLRiver service.

In plain words
What is it for?
Use it to inspect rankings, search verticals, and URL indexation across Google and Yandex.
Why use it?
It gathers search visibility data without changing websites or search settings. It requires XMLRiver account details and pricing settings to run.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Written for no agent in particular: it speaks MCP, so any client can run it.

One of 8 entries in server.json upstream. Installing this one merges just its entry into your config; the other 7 are separate, each on its own page.

not rated 3repo 6d ago A scan tokens not measured original MIT

Good fit Use it to inspect rankings, search verticals, and URL indexation across Google and Yandex.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/antohins/seo-tools-mcp/aparser-seo-tools-mcp-xmlriver
View source ↗ antohins/seo-tools-mcp
Install

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.

Clone the repo
git clone --depth 1 https://github.com/antohins/seo-tools-mcp

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote 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.

agentmods badge for seo-tools-mcp-xmlriver

README.md
[![agentmods](https://agentmods.dev/badge/mcp/antohins/seo-tools-mcp/aparser-seo-tools-mcp-xmlriver/github.svg)](https://agentmods.dev/mcp/antohins/seo-tools-mcp/aparser-seo-tools-mcp-xmlriver)
Your own site
<a href="https://agentmods.dev/mcp/antohins/seo-tools-mcp/aparser-seo-tools-mcp-xmlriver"><img src="https://agentmods.dev/badge/mcp/antohins/seo-tools-mcp/aparser-seo-tools-mcp-xmlriver/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.

agentmods 80×15 button for seo-tools-mcp-xmlriver

Your own site · 80×15
<a href="https://agentmods.dev/mcp/antohins/seo-tools-mcp/aparser-seo-tools-mcp-xmlriver"><img src="https://agentmods.dev/badge/mcp/antohins/seo-tools-mcp/aparser-seo-tools-mcp-xmlriver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

seo-tools-mcp-xmlriver 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.

servers/aparser/server.json · 15 lines

What it actually says

{
  "seo-tools-mcp-xmlriver": {
    "command": "npx",
    "args": [
      "-y",
      "seo-tools-mcp-xmlriver"
    ],
    "env": {
      "XMLRIVER_USER": "",
      "XMLRIVER_KEY": "",
      "XMLRIVER_EXCLUDE_DOMAINS": "",
      "XMLRIVER_PRICE_PER_CALL": ""
    }
  }
}
Same file

What else server.json configures

This page is one entry in a file that holds 8. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

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.

  1. 11d ago First seen · 15 lines scan A 3b4b2e3e51ba

Subscribe to this mod's changes

seo-tools-mcp-xmlriver is an MCP server published in the GitHub repository antohins/seo-tools-mcp (3 stars, last pushed 6d 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.

Marketing and SEOclaudemcpmodel-context-protocolsearch-consoleseoyandex
Related

Other mcp servers, from other repositories

xmlriver-mcp

MCP server for XMLRiver — Google/Yandex SERP parsing and Wordstat frequency data via XML API. Runs locally from the xmlriver-mcp Python package.

artgas1/xmlriver-mcp · not measured

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.

CorgiCorner/bisibility-mcp · not measured

yandex-webmaster-mcp

Query Yandex Webmaster indexing, queries, diagnostics and backlinks, and recrawl, via an AI agent. Runs locally from the @boxlab/yandex-webmaster-mcp npm package. Needs 2 environment variables to run.

BoxLab-Ltd/yandex-webmaster-mcp · not measured

yandex-webmaster

Model Context Protocol (MCP) server for Yandex Webmaster — query indexing, search queries, diagnostics and backlinks, and submit URLs for recrawl through an AI agent. Runs locally from the @boxlab/yandex-webmaster-mcp npm package.

BoxLab-Ltd/yandex-webmaster-mcp · not measured

tracetify-mcp

Find competitors, trace how they grew, watch what they ship — plus your Search Console. Runs locally from the tracetify-mcp npm package. Needs 1 environment variable to run.

tracetify/tracetify-mcp · not measured

google-search-console-mcp

MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection. Runs locally from the @ni-c/google-search-console-mcp npm package. Needs 11 environment variables to run.

ni-c/google-search-console-mcp · not measured