About Russia Access
Russia Access is a remote MCP server and REST API for x402 market checks and web content retrieval through Russian IP addresses. It is intended for AI agents that need endpoint and seller intelligence before payment or access to sites that block foreign traffic.
Key features
- 01Check x402 endpoint liveness and prices
- 02Search services by task and price
- 03Assess seller reputation and buyer patterns
- 04Fetch pages through Russian IPs
- 05Fetch web pages by country
- 06Inspect domains and marketplace listings
Use cases
- 01Check an x402 service before making an irreversible payment
- 02Find services within a task and price range
- 03Review seller activity for signs of manufactured volume
- 04Retrieve content from Russian sites that block foreign traffic
MCP support
The remote MCP server at `https://ruscrape.com/mcp` exposes tools for x402 market intelligence, Russian and country-specific web fetching, and related checks. MCP tools can use a prepaid balance, with failed-call charges refunded automatically.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://ruscrape.com/mcpclaude mcp add --transport http ruscrape https://ruscrape.com/mcp{"mcpServers":{"ruscrape":{"type":"http","url":"https://ruscrape.com/mcp"}}}Open in Cursor{"servers":{"ruscrape":{"type":"http","url":"https://ruscrape.com/mcp"}}}Open in VS Code{"mcpServers":{"ruscrape":{"type":"http","url":"https://ruscrape.com/mcp"}}}{"mcpServers":{"ruscrape":{"serverUrl":"https://ruscrape.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
9| Parameter | Type | Required | Description |
|---|---|---|---|
| agent_id | string | Yes | |
| url | string | Yes | |
| country | string | No | |
| residential | boolean | No | |
| render | boolean | No |
Details
From the project READMEx402 Market Intelligence + Russian Web Access — for AI Agents
Remote MCP server + REST API. Two things agents can't get anywhere else: verified intelligence about the x402 economy itself, and content from Russian sites that block foreign traffic.
- Live service: https://ruscrape.com
- MCP endpoint (streamable-http): https://ruscrape.com/mcp
- Official MCP Registry:
com.ruscrape/russia-access
Why the market intelligence matters
x402 payments are irreversible — there is no dispute button. An agent that pays a dead endpoint or a wash-trading farm simply loses the money. From our own measurements:
- 1 in 6 listed services is dead;
- 76 % of Base volume goes to sellers with fewer than 25 unique buyers — six addresses with exactly 5 buyers each accounted for 45 % of top-100 revenue;
- 9 of the 12 largest recipients are absent from the public catalog altogether.
We have run daily snapshots of the catalog, prices, liveness and leaderboards since 2026-06-16. That history cannot be bought or reconstructed after the fact — which is what makes these answers possible at all.
Tools
Market intelligence
x402_service_check(agent_id, resource) # check an endpoint BEFORE paying it
x402_discovery(agent_id, q, max_price_usd) # find a service by task and price (27k+ listings)
x402_seller_reputation(agent_id, address) # revenue, unique buyers, organic-vs-farm verdict
x402_service_check returns liveness from our own probes, the current and historical price, the
receiving address, and a verdict on whether that seller looks organic or manufactured.
Russian web access
fetch_ru(agent_id, url, residential=false) # URL in, content out, via a Russian IP
fetch_web(agent_id, url, country="ru") # same for any country
Works on sites that block foreign traffic: Wildberries, Ozon, Yandex Market, hh.ru, Avito.
Set residential=true for hard antibot sites.
Note on scope: Russian government registries (nalog.ru and similar) are not reachable through this channel — our residential provider blocks government domains outright. We would rather say so than take payment for a request that will fail.
Other tools: get_ru_proxy, run_code, marketplace_search, check_domain, topup_balance,
check_balance.
Connect
Add a remote MCP server pointing at https://ruscrape.com/mcp (transport: streamable-http).
Machine-readable
| Resource | URL |
|---|---|
| MCP manifest | https://ruscrape.com/.well-known/mcp.json |
| llms.txt | https://ruscrape.com/llms.txt |
| OpenAPI | https://ruscrape.com/openapi.json |
| Pricing | https://ruscrape.com/pricing |
| Plugin manifest | https://ruscrape.com/.well-known/ai-plugin.json |
Payment
Two ways, both without human signup:
- x402 / USDC on Base — call the paid endpoint, get
HTTP 402with payment terms, pay, retry. Direct HTTP endpoints:/x402/market/service($0.02),/x402/market/search($0.01),/x402/market/seller($0.05),/x402/fetch($0.015). - Prepaid balance (MCP tools) —
topup_balancevia x402/USDC or RUB, then call tools. On a failed call the charge is refunded automatically;Idempotency-Keysupported.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.