mcp-registry/com.ruscrape/russia-access · v1.27.2
As of 2026-10-18 13:07 UTC, the Ruscrape Russia Access MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 34 outages in 90 days, with a median recovery of 8 minutes.
Check x402 endpoints before paying: liveness, price history, farm detection. Plus RU web access.
Claude Code
claude mcp add --transport http ruscrape-russia-access-mcp-server https://ruscrape.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ruscrape-russia-access-mcp-server": {
"type": "http",
"url": "https://ruscrape.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
35 parameter(s) across 12 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,448 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (run_code, name): "run_code(code, timeout, agent_id, language)"
Declare destructiveHint/readOnlyHint on these tools and say plainly in the description what runs, where, and with what limits. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.ruscrape%2Frussia-access/fixes
{
"name": "check_balance",
"description": "Get agent balance in minor units (kopecks).",
"inputSchema": {
"type": "object",
"title": "check_balanceArguments",
"required": [
"agent_id"
],
"properties": {
"agent_id": {
"type": "string",
"title": "Agent Id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_domain",
"description": "Check if a domain is available (.com/.ru/.рф). Free, no balance needed.",
"inputSchema": {
"type": "object",
"title": "check_domainArguments",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"title": "Domain"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "fetch_ru",
"description": "Russia specialization of fetch_web (country='ru'): content of any Russian site/API through a\n Russian IP (Wildberries, Ozon, Yandex Market, hh.ru, Avito). residential=true for hard antibot.",
"inputSchema": {
"type": "object",
"title": "fetch_ruArguments",
"required": [
"agent_id",
"url"
],
"properties": {
"url": {
"type": "string",
"title": "Url"
},
"agent_id": {
"type": "string",
"title": "Agent Id"
},
"residential": {
"type": "boolean",
"title": "Residential",
"default": false
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.ruscrape/russia-access"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.ruscrape/russia-access"}) over MCP.
fetch_web ~258 tokensx402_service_check ~202 tokensrun_code ~170 tokensx402_seller_reputation ~169 tokenssubmit_survey ~165 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.ruscrape%2Frussia-access?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.ruscrape%2Frussia-access?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ruscrape%2Frussia-access.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ruscrape%2Frussia-access.svg :target: https://glimind.com/server/mcp-registry%2Fcom.ruscrape%2Frussia-access?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e6c7db3521bd9fc1…, first seen 2026-10-17, included at leaf 3494 of 22,008. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable other servers · most reliable web servers · most reliable code servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 13:07 UTC, the Ruscrape Russia Access MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 34 outages in 90 days, with a median recovery of 8 minutes.
Ruscrape Russia Access MCP server advertises 12 tools, including check_balance, check_domain, fetch_ru, fetch_web, get_ru_proxy.
Point your MCP client at this streamable-http endpoint: https://ruscrape.com/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.