Currency Minor Unit Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.3Updated Oct 24, 2026

Finds the money lines that send the wrong amount to a payment API: the x100 that charges 100x in JPY

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

A local MCP server that scans code for money amounts sent to payment APIs in the wrong minor unit, such as a 100x overcharge in JPY.

What you can do
Checks money values in code against the minor-unit conventions of currencies, flagging amounts that would be sent to a payment API in the wrong unit. Surfaces cases such as a x100 conversion that would charge 100 times the intended amount in a zero-decimal currency like JPY. Runs as a local command-line tool started by the assistant. The supplied README does not document its tools or usage.
When to use it
Useful when reviewing or maintaining code that formats amounts for payment APIs, especially across currencies with different decimal places, and you want an automated check for unit mistakes before they reach production.
Requirements
Runs locally as a Node.js process via npx from the npm package; no authentication, environment variables or headers are declared.
Before you install
The README content does not match the server's stated purpose and gives no usage details, so verify what it actually does before relying on it. It inspects code, so review what files it reads.

Installation

In SourceWeft

  1. Open Currency Minor Unit Lint 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

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

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

Version history

2
  1. v0.1.3LatestSep 19, 2026
  2. v0.1.1Sep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.