What can you do with this server?

This MCP server creates Robokassa payment links with MD5 signatures and checks invoice status. * create_invoice — Generate a Robokassa payment URL with an MD5 signature, with optional 54-FZ fiscal receipt. * Required: outSum (payment amount in RUB, > 0), invId (unique order ID; 0 = auto-generate), description (order description, ≤ 100 chars). * Optional: email (buyer email for receipt), items (receipt line items, each requiring name, quantity, sum, and VAT tax rate: none/vat0/vat10/vat110/vat20/vat120), culture (ru or en payment UI language), expirationDate (ISO 8601 invoice lifetime). * check_invoice — Check an invoice's payment status by invoice number via the OpStateExt XML interface (requires invId > 0). * Auth/config: Requires ROBOKASSA_LOGIN, ROBOKASSA_PASSWORD1 (signature), ROBOKASSA_PASSWORD2 (status checks); optional ROBOKASSA_TEST=true for test mode. * Limits: Both tools are read/URL-generation only and declare taskSupport: forbidden (no long-running task support).

How do I use @theyahia/robokassa-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@theyahia/robokassa-mcp create an invoice for 1000 RUB with order ID 12345" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

@theyahia/robokassa-mcp

MCP server for Robokassa payment API. 2 tools for invoice creation (with MD5 signature) and status checking.

npm license

Quick Start

Claude Desktop

{
  "mcpServers": {
    "robokassa": {
      "command": "npx",
      "args": ["-y", "@theyahia/robokassa-mcp"],
      "env": {
        "ROBOKASSA_LOGIN": "your-login",
        "ROBOKASSA_PASSWORD1": "your-password1",
        "ROBOKASSA_PASSWORD2": "your-password2"
      }
    }
  }
}

Claude Code

claude mcp add robokassa -e ROBOKASSA_LOGIN=login -e ROBOKASSA_PASSWORD1=pass1 -e ROBOKASSA_PASSWORD2=pass2 -- npx -y @theyahia/robokassa-mcp

Cursor / Windsurf

{
  "robokassa": {
    "command": "npx",
    "args": ["-y", "@theyahia/robokassa-mcp"],
    "env": {
      "ROBOKASSA_LOGIN": "your-login",
      "ROBOKASSA_PASSWORD1": "your-password1",
      "ROBOKASSA_PASSWORD2": "your-password2"
    }
  }
}

Related MCP server: @theyahia/yookassa-mcp

Tools

Tool	Description
`create_invoice`	Create payment URL with MD5 signature, optional 54-FZ receipt
`check_invoice`	Check invoice status via OpStateExt XML interface

Auth

Variable	Required	Description
`ROBOKASSA_LOGIN`	Yes	Merchant login
`ROBOKASSA_PASSWORD1`	Yes	Password 1 (for payment signature)
`ROBOKASSA_PASSWORD2`	Yes	Password 2 (for status check signature)
`ROBOKASSA_TEST`	No	Set to "true" for test mode

HTTP Transport

HTTP_PORT=3000 npx @theyahia/robokassa-mcp
# or
npx @theyahia/robokassa-mcp --http 3000

Endpoints: POST /mcp (JSON-RPC), GET /health (status).

Skills

skill-create-invoice -- create a Robokassa payment URL with MD5 signature
skill-check-payment -- check invoice status via OpStateExt

License

MIT

Available Tools

2 tools

check_invoiceA

Проверить статус счёта Robokassa по номеру (OpStateExt).

ParametersJSON Schema

Name	Required	Description	Default
`invId`	Yes	Номер счёта для проверки статуса

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description only states 'check status' with no details on behavior, authentication, error handling, or side effects. Insufficient for a read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no fluff. Includes API method name (OpStateExt) for specificity. Efficiently front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool with one param and clear purpose, but lacks any description of output/returned status. Adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, description adds no new meaning beyond the schema's own 'description' for invId. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'check', the resource 'invoice status', and the method 'by number (OpStateExt)'. It distinguishes from sibling 'create_invoice' which is for creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Context implies use for checking existing invoices, contrasting with 'create_invoice'. No explicit when-not or alternative usage, but clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create_invoiceB

Создать счёт Robokassa. Возвращает ссылку на оплату с MD5-подписью.

ParametersJSON Schema

Name	Required	Description
`email`	No	Email покупателя для чека
`invId`	Yes	Номер счёта (уникальный ID заказа). 0 = автоматически
`items`	No	Позиции чека 54-ФЗ (если нужна фискализация)
`outSum`	Yes	Сумма платежа в рублях
`culture`	No	Язык интерфейса оплаты
`description`	Yes	Описание заказа (до 100 символов)
`expirationDate`	No	Срок жизни счёта в формате ISO 8601 (например 2025-12-31T23:59:59)

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions returning a payment link with MD5 signature but fails to disclose mutation behavior, required permissions, or side effects. For a creation tool, more transparency is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, conveying the core purpose in two sentences. It effectively communicates the essential information without waste, though more detail could be beneficial.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters (3 required) and no output schema, the description does not explain the return structure beyond 'link with MD5 signature' or cover error handling, idempotency, or configuration needs. It feels incomplete for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all parameters have individual descriptions. The tool description adds no additional meaning beyond the schema, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a Robokassa invoice and returns a payment link with an MD5 signature. The verb 'create' and resource 'invoice' are unambiguous, and it distinguishes from the sibling 'check_invoice' which checks invoices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as the sibling 'check_invoice'. It lacks context on prerequisites, typical use cases, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesv1.1.0Jul 28, 2026
- First observedcheck_invoice
- First observedcreate_invoice

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-07-28 07:30 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one creates an invoice, the other checks its status. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern in snake_case: create_invoice, check_invoice.

Tool Count3/5

With only 2 tools, the surface feels thin for a payment invoice service. While it covers basic operations, it is at the lower end of the acceptable range.

Completeness3/5

The set provides create and check (read) operations but misses other lifecycle actions like cancel or refund, resulting in notable gaps for a typical payment workflow.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

MCP Billing Gateway A
io.github.sapph1re
Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code.
Payments & Billing
1212
Recurly
io.github.pipeworx-io
MCP server for recurly
Payments & Billing Finance
1
hostinger-api-mcpOAuth
io.github.hostinger
MCP server for Hostinger API
Cloud Platforms Developer Tools
1155
fastmcpruntime-mcp
com.clauxel.fastmcpruntime
A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r
Agent Orchestration Monitoring
2

Related MCP Servers

@theyahia/tkassa-mcp
Payments & Billing Finance
theYahia
A
license
Not graded
quality
F
maintenance
MCP server for T-Kassa (T-Bank/Tinkoff) payment API. Provides 16 tools for payments, refunds, recurring charges, customer management, saved cards, SBP, receipts, and T-Invest portfolio.
Updated 12 days ago (2026-09-05 14:03 UTC)
38 npm
MIT
@theyahia/yookassa-mcp
Payments & Billing Finance E-commerce & Retail
theYahia
A
license
A
quality
B
maintenance
MCP server for YooKassa API enabling payments, refunds, receipts, payouts, webhooks, and more via 20 tools.
Updated 14 days ago (2026-09-03 04:50 UTC)
20
68 npm
4
MIT
robokassa-mcp
Payments & Billing Finance
artgas1
A
license
A
quality
D
maintenance
MCP server for the Robokassa payment gateway, enabling AI agents to create invoices, check payments, process refunds, manage recurring subscriptions, and handle fiscal receipts via natural language.
Updated 5 months ago (2026-04-23 23:36 UTC)
18
1
MIT
factura-uz-mcp
Finance Payments & Billing
theYahia
A
license
A
quality
D
maintenance
MCP server for Factura.uz electronic invoicing system (Uzbekistan). Supports creating, signing, accepting, and rejecting e-invoices, plus company and product lookups.
Updated 6 months ago (2026-04-01 16:28 UTC)
8
7 npm
MIT

@theyahia/robokassa-mcp

Quick Start

Claude Desktop

Claude Code

Cursor / Windsurf

Tools

Auth

HTTP Transport

Skills

License

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

@theyahia/tkassa-mcp

@theyahia/yookassa-mcp

robokassa-mcp

factura-uz-mcp