Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.artgas1/robokassa-mcp

PYPI · ROBOKASSA-MCP

Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage).

Available components

0 this week 81 Trust /100

Last scanned (20 hours ago)

Scores higher than 80% of PyPI servers

Category Finance and Payments

Recent critical change

GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 211 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2215 tokens (~123/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "refund_create" implies "refund" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 16 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 10 Nov 26 +1
    • Stability: 0.97 → pass security
  • 9 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/robokassa-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~2,215 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_split_invoice ~84

Build a URL for a multi-recipient (marketplace-style) split payment. Each split: `{merchantLogin, amount, description?}`. Sum of amounts must equal out_amount.

NameTypeReqDescription
description–––
email–––
inc_curr–––
inv_id–––
out_amountnumberyes–
splitsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

calc_out_sum ~132

Calculate the amount credited to the shop for a given customer payment. Useful for showing the commission / final sum in checkout UI. Signature: `<algorithm>(MerchantLogin:IncSum:Password#1)`.

NameTypeReqDescription
algorithmstring–Signature algorithm configured in the cabinet.
inc_curr_label––Specific payment method label from `list_currencies`. If omitted, Robokassa calculates for the default method.
inc_sumnumberyesAmount the customer pays.
merchant_login––Falls back to ROBOKASSA_LOGIN.
password1––Falls back to ROBOKASSA_PASSWORD1.

Structured output declared, but exposes no named fields.

No examples provided.

check_payment ~119

Check the current state of a Robokassa payment by invoice ID. Uses the `OpStateExt` XML interface. Returns a structured summary including the state code (5/10/20/50/60/80/100), the OpKey (required later for initiating a refund via Refund/Create), sums, payment method, and any user-defined `Shp_*` parameters attached at checkout.

NameTypeReqDescription
algorithmstring––
inv_idintegeryes–
merchant_login–––
password2–––

Structured output declared, but exposes no named fields.

No examples provided.

create_invoice ~330

Build a signed Robokassa checkout URL + form fields for a new payment. Does NOT make an HTTP request — produces the URL to redirect the user to.

NameTypeReqDescription
algorithmstring–Signature hash algorithm.
culturestring–UI locale (`ru` / `en` / `kk`).
currency––Restrict to specific payment method (`IncCurrLabel`).
description––Human-readable order description.
email––Pre-fill customer email on the payment page.
inv_idintegeryesUnique invoice number. Pass 0 to let Robokassa assign one.
is_testboolean–Use sandbox checkout instead of production.
merchant_login––Shop ID. Falls back to ROBOKASSA_LOGIN env var.
out_sumnumberyesAmount to charge (any numeric type; normalized to 2 decimals).
password1––Password#1. Falls back to ROBOKASSA_PASSWORD1 env var.
receipt_items––Optional 54-ФЗ fiscal receipt items. Each item: `{name, quantity, sum, tax, payment_method, payment_object, nomenclature_code}`. Tax ∈ none / vat0 / vat5 / vat7 / vat10 / vat20 / vat105 / vat107 /…
receipt_sno––Taxation scheme (`osn` / `usn_income` / etc.).
shp_params––Extra `Shp_*` params echoed back in ResultURL. Keys may be passed without the `Shp_` prefix.

Structured output declared, but exposes no named fields.

No examples provided.

hold_cancel ~44

Release a hold without capturing the reserved funds.

NameTypeReqDescription
algorithmstring––
inv_idintegeryes–
merchant_login–––
password1–––

Structured output declared, but exposes no named fields.

No examples provided.

hold_confirm ~100

Capture previously-reserved funds for a held transaction. Cart can be reduced (smaller `receipt_items`) before capture, but not increased. Pass the same OutSum (possibly smaller) as the original hold.

NameTypeReqDescription
algorithmstring––
inv_idintegeryes–
merchant_login–––
out_sumnumberyes–
password1–––
receipt_items–––
receipt_sno–––

Structured output declared, but exposes no named fields.

No examples provided.

hold_init ~160

Build a checkout URL with StepByStep=true for two-step pre-auth. Funds are reserved on the card; use `hold_confirm` to capture or `hold_cancel` to release. Max hold window: 7 days. Notification for successful hold is delivered to ResultURL2 (not the standard ResultURL). Requires prior agreement with Robokassa and only works with card payments.

NameTypeReqDescription
algorithmstring––
culturestring––
description–––
email–––
inv_idintegeryes–
is_testboolean––
merchant_login–––
out_sumnumberyes–
password1–––
receipt_items–––
receipt_sno–––

Structured output declared, but exposes no named fields.

No examples provided.

init_recurring_parent ~122

Build a checkout URL marking the payment as a recurring parent. After the user pays, the shop can silently charge subsequent amounts via `recurring_charge` citing this invoice's `inv_id`.

NameTypeReqDescription
algorithmstring––
culturestring––
description–––
email–––
inv_idintegeryes–
is_testboolean––
merchant_login–––
out_sumnumberyes–
password1–––
receipt_items–––
receipt_sno–––

Structured output declared, but exposes no named fields.

No examples provided.

list_currencies ~146

List payment methods / currencies available to a Robokassa shop. Returns the full catalogue grouped by payment family (BankCard, SBP, SberPay, YandexPay, etc.) with per-method Label, Alias, Name, and min/max transaction bounds where applicable. The Label values are what you pass as `IncCurrLabel` when calling `create_invoice` to restrict the user to a specific payment method. No password / signature required — GetCurrencies is a public endpoint.

NameTypeReqDescription
languagestring–UI language for Name fields (`ru` / `en`).
merchant_login––Shop identifier. Falls back to ROBOKASSA_LOGIN env var.

Structured output declared, but exposes no named fields.

No examples provided.

partner_refund ~106

Alternative refund path via Partner API (for CPA / SaaS integrators). Merchant-only users should prefer `refund_create` instead (uses Password#3). Partner API requires `RoboxPartnerId` and partner-specific auth headers — typically `{"Authorization": "Bearer <partner-jwt>"}`.

NameTypeReqDescription
auth_headersobjectyes–
op_keystringyes–
receipt–––
refund_sum–––
robox_partner_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

recurring_charge ~124

Silently charge a recurring subscription payment. `previous_inv_id` must be the inv_id of an already-paid parent (created with `init_recurring_parent`). Response `"OK<InvId>"` means accepted, NOT captured — verify via `check_payment`.

NameTypeReqDescription
algorithmstring––
description–––
merchant_login–––
new_inv_idintegeryes–
out_sumnumberyes–
password1–––
previous_inv_idintegeryes–
receipt_items–––
receipt_sno–––

Structured output declared, but exposes no named fields.

No examples provided.

refund_create ~83

Initiate a refund for a successful Robokassa payment. Requires `op_key` — obtained from `check_payment` (OpStateExt) or the `Result2` webhook payload for the original operation.

NameTypeReqDescription
algorithmstring––
items–––
op_keystringyes–
password3–––
refund_sum–––

Structured output declared, but exposes no named fields.

No examples provided.

refund_status ~34

Check the current state of a previously-created refund request.

NameTypeReqDescription
request_idstringyesGUID returned by `refund_create()`.

Structured output declared, but exposes no named fields.

No examples provided.

second_receipt_create ~207

Emit a final (second) 54-ФЗ fiscal receipt after an advance/prepayment sale. For merchants using Robokassa Fiscal. `merchant_id` is the Fiscal merchantId (e.g. `robokassa_sell`); `origin_id` is the InvId of the original operation. Max 2 receipts per operation. items: `[{name, quantity, sum, tax, payment_method, payment_object}]`. payments: typically `[{type: 2, sum: <total>}]` for offsetting a prepayment. client: `{email}` or `{phone}`.

NameTypeReqDescription
clientobjectyes–
itemsarrayyes–
merchant_idstringyes–
origin_idstringyes–
password1–––
paymentsarrayyes–
receipt_idstringyes–
sno–––
totalnumberyes–
urlstringyes–
vats–––

Structured output declared, but exposes no named fields.

No examples provided.

second_receipt_status ~59

Check registration status of a 54-ФЗ fiscal receipt. Use `merchant_id="robokassa_state"` for status lookups.

NameTypeReqDescription
merchant_idstringyes–
password1–––
receipt_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

send_sms ~82

Send an SMS via Robokassa's SMS service. Paid feature — requires a non-zero SMS balance in the cabinet. Phone must be in international format (e.g. `79991234567`).

NameTypeReqDescription
algorithmstring––
merchant_login–––
messagestringyes–
password1–––
phonestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

verify_result_signature ~160

Verify the SignatureValue on a Robokassa ResultURL request. Robokassa POSTs payment notifications to the merchant's ResultURL after a successful checkout. The merchant must verify the signature to confirm the notification is authentic, then respond with the string returned by `build_ok_response(inv_id)` — otherwise Robokassa retries.

NameTypeReqDescription
algorithmstring–Signature algorithm configured in the cabinet.
paramsobjectyesForm-encoded body from the ResultURL request. Must contain OutSum, InvId, SignatureValue. Any `Shp_*` parameters included in the body are automatically incorporated into signature verification.
password2––Shop's Password#2. Falls back to ROBOKASSA_PASSWORD2 env var.

Structured output declared, but exposes no named fields.

No examples provided.

verify_success_signature ~123

Verify the SignatureValue on a Robokassa SuccessURL redirect. SuccessURL is the browser-side redirect after payment completes. Unlike ResultURL it does NOT mean the payment is credited — only that the user returned to the success page. Still, verifying the signature guards against CSRF / tampering.

NameTypeReqDescription
algorithmstring–Signature algorithm configured in the cabinet.
paramsobjectyesQuery-string params from the SuccessURL GET request.
password1––Shop's Password#1. Falls back to ROBOKASSA_PASSWORD1 env var.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.artgas1/robokassa-mcp server?

io.github.artgas1/robokassa-mcp runs locally as a PyPI package, launched with uvx robokassa-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · robokassa-mcp

# add to Claude Code
claude mcp add artgas1-robokassa-mcp -- uvx robokassa-mcp
Common questions

What is the io.github.artgas1/robokassa-mcp server?

io.github.artgas1/robokassa-mcp is listed in the public MCP registry as io.github.artgas1/robokassa-mcp. Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage). This page covers its PyPI package (robokassa-mcp).

Is the io.github.artgas1/robokassa-mcp server safe to use?

io.github.artgas1/robokassa-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.artgas1/robokassa-mcp server expose?

io.github.artgas1/robokassa-mcp exposes 18 tools: check_payment, refund_create, refund_status, create_invoice, verify_result_signature, and 13 more. Their descriptions and schemas cost roughly 2,215 tokens of context every time the server is loaded.

Is the io.github.artgas1/robokassa-mcp server still maintained?

io.github.artgas1/robokassa-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.artgas1/robokassa-mcp server under?

io.github.artgas1/robokassa-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.artgas1/robokassa-mcp server?

VerifyMCP ran 16 checks on io.github.artgas1/robokassa-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.