Xmlriver Mcp
@artgas1
About Xmlriver Mcp
First MCP server for XMLRiver — Russian-focused SEO API. Provides Google/Yandex SERP parsing, Yandex Wordstat keyword frequency data, and URL indexing checks via XML API. Fills the gap for Russian SEO research and Yandex-aware analysis in Claude / Cursor / Windsurf.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"xmlriver": {
"command": "uvx",
"args": [
"xmlriver-mcp"
],
"env": {
"XMLRIVER_USER": "<your_user_id>",
"XMLRIVER_KEY": "<your_api_key>"
}
}
}
}Tools
9Parse Google SERP for a query — country, language, device, page, date filter, extra blocks (ads, FAQ, knowledge graph, AI Overview)
Parse Yandex SERP — region, language, device, page, date filter, extra blocks
Yandex Search API v2 (official) via XMLRiver — cleaner structured output
Yandex Wordstat keyword frequency, device breakdown, history, similar queries
Check if URL is indexed in Google or Yandex
Current XMLRiver balance in rubles
Current XMLRiver tariff name (Basic / Pro / Mega / Giga)
Tariff expiration date (for prepay tariffs)
Cost per 1000 requests for a given engine (google / yandex / yaxml / wordstat)
Overview
What is Xmlriver Mcp?
An MCP server for XMLRiver that provides Google and Yandex SERP parsing, Yandex Wordstat keyword frequency data, and indexation checks via the XML API. It is designed for Claude, Cursor, and Windsurf, filling a gap for Russian SEO research and Yandex‑aware analysis. Pay‑as‑you‑go pricing (≈25 ₽ per 1k requests on the Basic tariff).
How to use Xmlriver Mcp?
Install and run with uvx xmlriver-mcp. Set the XMLRIVER_USER (numeric ID) and XMLRIVER_KEY (40‑character hex) environment variables in your MCP client configuration (Claude Desktop, Claude Code, or Cursor). All tools are invoked via the MCP protocol and are read‑only.
Key features of Xmlriver Mcp
- Google SERP parsing with country, language, device, and extra block detection (ads, FAQ, knowledge graph, AI Overview)
- Yandex SERP parsing with region, language, and device support
- Yandex Wordstat keyword frequency, history, and similar queries
- URL indexation check for Google and Yandex
- Account operations: balance, tariff, cost per 1k requests
- All tools are read‑only with
readOnlyHint: true - Retry strategy: 3 attempts with exponential backoff on network errors
Use cases of Xmlriver Mcp
- SEO position tracking – monitor your own and competitor rankings on Yandex and Google
- Keyword research – validate demand and seasonality via Yandex Wordstat
- Featured snippet hunting – see which pages own answer boxes, knowledge graphs, and zero‑position results
- Indexation monitoring – check new URLs for Google and Yandex indexing after publication
- Cross‑region comparison – compare search results for the same query across different countries and regions
FAQ from Xmlriver Mcp
What authentication is required?
Register at xmlriver.com, top up your balance (minimum ≈100 ₽), and retrieve your numeric user ID and 40‑character hex key from the dashboard. Set XMLRIVER_USER and XMLRIVER_KEY as environment variables.
What are the runtime requirements?
Python 3.10 or later. No external SDK is needed; the server uses httpx, FastMCP, and a custom XML parser.
Where does the data come from?
All data is fetched from the XMLRiver API, which in turn queries Google and Yandex SERPs and Yandex Wordstat.
What are the known limits?
The XMLRiver API uses HTTP only (not HTTPS). The API key can be rotated from the dashboard if compromised. The MCP server uses stdio transport and logs only to stderr.
How is pricing structured?
Pricing depends on the tariff. For example, the Basic tariff charges 25 ₽ per 1,000 requests for Google, Yandex, and Wordstat; higher tiers (Pro, Mega, Giga) offer lower per‑request costs. Use the get_balance and get_cost tools to monitor spend.
Frequently asked questions
What authentication is required?
Register at xmlriver.com, top up your balance (minimum ≈100 ₽), and retrieve your numeric `user` ID and 40‑character hex `key` from the dashboard. Set `XMLRIVER_USER` and `XMLRIVER_KEY` as environment variables.
What are the runtime requirements?
Python 3.10 or later. No external SDK is needed; the server uses httpx, FastMCP, and a custom XML parser.
Where does the data come from?
All data is fetched from the XMLRiver API, which in turn queries Google and Yandex SERPs and Yandex Wordstat.
What are the known limits?
The XMLRiver API uses HTTP only (not HTTPS). The API key can be rotated from the dashboard if compromised. The MCP server uses stdio transport and logs only to stderr.
How is pricing structured?
Pricing depends on the tariff. For example, the Basic tariff charges 25 ₽ per 1,000 requests for Google, Yandex, and Wordstat; higher tiers (Pro, Mega, Giga) offer lower per‑request costs. Use the `get_balance` and `get_cost` tools to monitor spend.
Basic information
More Data & Analytics MCP servers
CoinLobster
CoinLobsterThe only MCP server with live whale trades across 15 exchanges plus on-chain DEX flow. Smart Money Radar, real liquidations and outcome-scored signals. No API key required.
Kinetic Pricing
Kinetic PricingKinetic Pricing lets you run pricing research with your own customers and manage the work around each decision. Create Van Westendorp, Gabor-Granger, MaxDiff, and choice-based conjoint studies; preview and launch surveys
Octolens
OctolensGive your AI agents every brand mention across the internet — 15+ platforms, AI-filtered, one structured feed.
OrbitWan.io
Wanchain explorer data and analytics: addresses, transactions, tokens, validators, cross chain transfers, plus OrbitPay prepaid premium data (x402).
Signal Nodus SEC Filings
Signal NodusPrimary-source SEC intelligence for AI agents, delivered over MCP. 27 tools: year-over-year filing diffs, 8-K material events, 13D/13G activist stakes, insider Form 4 trades, 13F institutional holdings, IPO pipeline, ful
Comments