mcp-registry/com.payforapi/saymon-ru-data-api · v1.30.0
As of 2026-10-26 18:08 UTC, the Payforapi Saymon Ru Data Api MCP server is degraded with a Glimind reliability score of 56/100 (grade D). Over the last 30 days it answered 90.8% of Glimind's liveness checks. It had 852 outages in 90 days, with a median recovery of 7 minutes.
Russian company lookup (EGRUL/INN), Cyrillic search, RU page to Markdown. Pay per call in USDC.
Point your MCP client at this streamable-http endpoint: https://payforapi.com/mcp
Reachable 90.8% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
32 parameter(s) across 13 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 →
13 of 13 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 →
Handshake + tools/list takes ~2,402 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.
In the last 30 days: 7 tool(s) removed and 0 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 13 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.payforapi%2Fsaymon-ru-data-api/fixes
{
"name": "fns_npd_check",
"description": "Статус самозанятого (НПД) по ИНН через реестр ФНС. $0.01 USDC",
"inputSchema": {
"type": "object",
"title": "fns_npd_checkArguments",
"required": [
"inn"
],
"properties": {
"inn": {
"type": "string",
"title": "Inn"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "inn_lookup",
"description": "Проверка российского юрлица по ИНН (ЕГРЮЛ). $0.01 USDC",
"inputSchema": {
"type": "object",
"title": "inn_lookupArguments",
"required": [
"inn"
],
"properties": {
"inn": {
"type": "string",
"title": "Inn"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "pochta_address",
"description": "Почта России: нормализация российского адреса (индекс, регион, улица, дом). $0.01 USDC",
"inputSchema": {
"type": "object",
"title": "pochta_addressArguments",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"title": "Address"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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.payforapi/saymon-ru-data-api"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.payforapi/saymon-ru-data-api"}) over MCP.
pochta_delivery ~231 tokenspochta_tariff ~213 tokenspochta_offices ~148 tokenspochta_delivery_time ~137 tokensmoex_quote ~104 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.payforapi%2Fsaymon-ru-data-api?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.payforapi%2Fsaymon-ru-data-api?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.payforapi%2Fsaymon-ru-data-api.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.payforapi%2Fsaymon-ru-data-api.svg :target: https://glimind.com/server/mcp-registry%2Fcom.payforapi%2Fsaymon-ru-data-api?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:83e37640d37bceb3…, first seen 2026-10-17, included at leaf 17589 of 74,609. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable data servers · most reliable productivity servers · most reliable search servers · most reliable web 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-26 18:08 UTC, the Payforapi Saymon Ru Data Api MCP server is degraded with a Glimind reliability score of 56/100 (grade D). Over the last 30 days it answered 90.8% of Glimind's liveness checks. It had 852 outages in 90 days, with a median recovery of 7 minutes.
Payforapi Saymon Ru Data Api MCP server advertises 13 tools, including cbr_rates, fns_npd_check, inn_lookup, moex_quote, pochta_address.
Point your MCP client at this streamable-http endpoint: https://payforapi.com/mcp
Glimind scanned all 13 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.