Russian Web Data Access for AI Agents
Server Details
Fetch any Russian website or API via a Russian IP — flagship tool fetch_ru. Pay x402/RUB.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.6/5 across 9 of 9 tools scored.
There is overlap between fetch_ru and fetch_web, as fetch_ru is essentially a specialization of fetch_web with country='ru'. Additionally, get_ru_proxy provides an alternative way to access Russian sites, which may cause confusion. Other tools are distinct.
All tool names follow a consistent verb_noun snake_case pattern (e.g., check_balance, fetch_web, topup_balance). No mixed conventions or unpredictable variations.
9 tools is well-scoped for a server focused on Russian web data access, covering fetching, proxies, balance management, domain operations, and auxiliary functions. Each tool justifies its presence.
Core web fetching is covered, but minor gaps exist: no tool for managing proxies beyond acquisition, no listing of supported countries or features, and run_code seems peripheral to the main purpose.
Available Tools
9 toolscheck_balanceInspect
Get agent balance in minor units (kopecks).
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
check_domainInspect
Check if a domain is available (.com/.ru/.рф). Free, no balance needed.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes |
fetch_ruInspect
Russia specialization of fetch_web (country='ru'): content of any Russian site/API through a Russian IP (Wildberries, Ozon, Yandex Market, gov registries, banks). residential=true for hard antibot.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| agent_id | Yes | ||
| residential | No |
fetch_webInspect
Give a URL of ANY website or API — get its content (HTML/JSON) fetched through an IP of the chosen country (country='ru','us','de','gb',...). Flagship tool — URL in, content out, no proxy setup. Specialty: country='ru' unlocks Russia-only sites that block foreign IPs (Wildberries, Ozon, Yandex Market, gov registries EGRUL/FNS, banks). Set residential=true for sites that block datacenter IPs. Set render=true to render JS in a real headless Chromium (SPA / JS-heavy / JS-challenge sites). Charged from agent balance; returns payment_required if insufficient (then topup_balance and retry).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| render | No | ||
| country | No | ru | |
| agent_id | Yes | ||
| residential | No |
get_ru_proxyInspect
Get a Russian IP proxy to access RU-only sites (Wildberries, Ozon, gov registries, banks) that block foreign IPs. Charged from agent balance; returns payment_required if insufficient (then call topup_balance and retry). Idempotent per agent.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| agent_id | Yes | ||
| period_days | No |
register_ru_domainInspect
Register a .ru/.рф domain (secondary service). Charged from balance.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | ||
| agent_id | Yes | ||
| idempotency_key | Yes |
run_codeInspect
Run agent code (python / javascript / bash) in an isolated sandbox (no network, CPU/RAM/time limits) and get stdout/stderr/exit_code back. Charged from agent balance; returns payment_required if insufficient (then topup_balance and retry).
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| timeout | No | ||
| agent_id | Yes | ||
| language | No | python |
submit_surveyInspect
Help improve this service: tell us what you need. question is one of: need_data (which Russian data sources you need), why_no_pay (if you didn't pay: price/payment_friction/ just_exploring/not_now), missing_service (what's missing), country_need (which country IP). Short answer.
| Name | Required | Description | Default |
|---|---|---|---|
| answer | Yes | ||
| agent_id | Yes | ||
| question | Yes |
topup_balanceInspect
Top up agent balance. rail: usdc (x402) or rub (YooKassa). Returns pay_url to complete payment.
| Name | Required | Description | Default |
|---|---|---|---|
| rail | No | usdc | |
| No | agent@domains-for-ai.app | ||
| agent_id | Yes | ||
| amount_minor | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!