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.

Monobank

NPM · MONOBANK-MCP-SERVER · SCANNED SEP 21

MCP server for Monobank API — currency rates, client info, and account statements

Available components

npm · monobank-mcp-server 94
0 this week 94 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to akutishevsky/monobank-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 49 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 415 tokens (~138/item across 3 items; 3 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 Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Monobank MCP server?

Monobank runs locally as an npm package, launched with npx -y monobank-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · monobank-mcp-server

# add to Claude Code
claude mcp add akutishevsky-monobank-mcp-server -- npx -y monobank-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "akutishevsky-monobank-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "monobank-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "akutishevsky-monobank-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "monobank-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add akutishevsky-monobank-mcp-server -- npx -y monobank-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "akutishevsky-monobank-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "monobank-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add akutishevsky-monobank-mcp-server --command npx --arg -y --arg monobank-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  akutishevsky-monobank-mcp-server:
    command: "npx"
    args: ["-y", "monobank-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "akutishevsky-monobank-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "monobank-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add akutishevsky-monobank-mcp-server -t stdio -c npx -a -y monobank-mcp-server
// mcp.json
{
  "mcpServers": {
    "akutishevsky-monobank-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "monobank-mcp-server"
      ]
    }
  }
}
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 Sept 26 +1
    • Package version: 1.1.1 → 1.3.0 functional
  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1
    • Security disclosure: unverified → fail ▼ functional
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 Sept 2026 · Analysed npm/monobank-mcp-server@1.3.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo akutishevsky/monobank-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/akutishevsky/monobank-mcp-server/.github/workflows/publish.yml@refs/tags/v1.3.0
Rekor log index 2321094896
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:befd5960ac7e4043979e02b83f7c924f95ae541d84b759c518b688aa5f6ea043915de7901b0bf0205268f73b3a8e25c2598343ba207ce54a4c00b9218

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~415 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
get_client_info ~104

Get information about the client together with the list of their accounts and jars. Requires the MONOBANK_API_TOKEN environment variable. Monobank permits only one request per 60 seconds, so the response is cached in memory for 60 seconds: calls made within that window return the cached data instead of failing with a rate-limit error. All monetary amounts are returned in currency units, not in cents. The account and jar identifiers returned by this tool can be passed to get_statement.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_currency_rates ~74

Get the list of currency exchange rates from Monobank. This is a public endpoint and does not require an API token. Monobank permits only one request per 5 minutes, so the response is cached in memory for 5 minutes: calls made within that window return the cached rates instead of failing with a rate-limit error.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_statement ~237

Get the Monobank statement for an account or jar between the {from} and {to} dates. Requires the MONOBANK_API_TOKEN environment variable. The maximum period for which a statement can be obtained is 31 days + 1 hour (2682000 seconds). Monobank permits only one request per 60 seconds, so every distinct account/date-range request is cached in memory for 60 seconds: repeating the same request within that window returns the cached statement instead of failing with a rate-limit error. All monetary amounts are returned in currency units, not in cents.

NameTypeReqDescription
accountstring–A unique identifier of the Monobank account or jar to build the statement for. Defaults to '0', which means the client's default account. Account and jar identifiers can be obtained from the get_clie…
fromstringyesThe start date of the statement period, in ISO 8601 YYYY-MM-DD format (UTC).
tostring–The end date of the statement period, in ISO 8601 YYYY-MM-DD format (UTC). The whole day is included. Defaults to the current moment when omitted.

No output schema declared.

No examples provided.

Common questions

What is the Monobank MCP server?

Monobank is an MCP server listed in the public MCP registry as io.github.akutishevsky/monobank-mcp-server. MCP server for Monobank API, currency rates, client info, and account statements. This page covers its npm package (monobank-mcp-server).

Is the Monobank MCP server safe to use?

Monobank scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Monobank MCP server expose?

Monobank exposes 3 tools: get_currency_rates, get_client_info, get_statement. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

Is the Monobank MCP server still maintained?

Monobank is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Monobank MCP server under?

Monobank declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.