Mcp Geracash

io.github.geraservicesukPublished by GitHub account geraservicesukv0.1.1Updated Oct 24, 2026

Cross-border remittance and wallet: send money, pay bills, FX, balances. OAuth+2FA for writes.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A local MCP server for GeraCash that lets an assistant handle cross-border remittances, bill payments, currency exchange and wallet balances.

What you can do
Send cross-border remittances and transfer money through the GeraCash wallet service. Pay bills from the wallet. Check balances and perform foreign-exchange operations. Write actions are protected by OAuth plus two-factor authentication.
When to use it
Useful when you want an assistant to help with GeraCash remittances, bill payments, FX or balance checks from a desktop setup, rather than switching to the GeraCash app or site.
Requirements
Runs as a local process over stdio, installed from the npm package @gera-services/mcp-geracash, so Node.js is needed. The GERACASH_API_URL environment variable sets the API base URL and defaults to the public GeraCash API. A GeraCash account with OAuth and two-factor authentication is needed for write operations. Desktop only.
Before you install
This server moves real money: transfers, bill payments and FX can be irreversible, so review every write action before approving it. Write operations require OAuth and two-factor authentication, so keep those credentials and codes private. Requests go to the GeraCash API at the configured GERACASH_API_URL, so a non-default URL sends account and transaction data to that host.

Installation

In SourceWeft

  1. Open Mcp Geracash in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.