Treasury Risk Analyzer

io.github.christianmatumonaPublished by GitHub account christianmatumonav0.1.2Updated Nov 3, 2026

Treasury risk, FX exposure, liquidity & payment decisions for AI CFO agents. Pay per call in USDC.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

Treasury Risk Analyzer's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Treasury Risk Analyzer 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

treasury-risk-mcp

MCP server for the Treasury Risk Analyzer: deterministic financial decision services for AI Treasury and CFO agents. It covers treasury risk, FX exposure, the liquidity forecast, and one question: "Can we safely execute this payment today?"

Each call is paid in USDC on Base via x402. There is no account, no API key and no subscription. Your agent pays per call from its own wallet, and only when the input is valid.

Tools

ToolPriceWhat it answers
describe_servicefreeWhat the service does, its prices, and whether payments are configured
get_example_inputfreeA valid example input for any paid tool
run_demofreeRuns a paid tool on fixed sample data and returns its real, full output (default: can we pay a EUR 750,000 invoice today?)
treasury_risk$0.10Volatility, Sharpe/Sortino/Calmar, VaR/CVaR, HHI concentration, risk contribution, correlated stress tests
fx_exposure$0.25Gross/net exposure by currency, natural hedges, FX stress scenarios, hedge priority
liquidity_forecast$0.50Daily cash projection, minimum cash and its date, buffer breach, liquidity status, optional DSO/DPO/DIO
treasury_decision$2.00PAY / REVIEW / DO_NOT_PAY for a payment, combining liquidity, FX and risk, with a confidence score

No LLM computes any figure: every metric is deterministic and documented in the response's methodology.

Install

Claude Desktop (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "treasury-risk": {      "command": "npx",      "args": ["-y", "treasury-risk-mcp"],      "env": {        "X402_PRIVATE_KEY": "0x…",        "MAX_PAYMENT_USD": "2.00"      }    }  }}

Claude Code:

bash
claude mcp add treasury-risk -e X402_PRIVATE_KEY=0x… -e MAX_PAYMENT_USD=2.00 -- npx -y treasury-risk-mcp
VariableDefaultMeaning
X402_PRIVATE_KEY(none)Private key of a Base wallet that holds USDC. Without it, paid tools only validate your input and return the price.
MAX_PAYMENT_USD2.00Hard per-call cap. A tool priced above it is refused before anything is signed.
TREASURY_API_URLproduction URLOverride the service URL.

Wallet safety: use a dedicated wallet that holds only a few USDC. The key stays in the MCP process on your machine. It is only used to sign an EIP-3009 USDC transfer for the exact price the service asks for, never more than MAX_PAYMENT_USD. No ETH is needed for gas, because the facilitator submits the transfer.

How payment works

  1. The tool sends your input to the API. Invalid input gets a free 400 and you are never charged.
  2. Valid input gets 402 Payment Required with the price.
  3. The server signs a USDC authorization for that price and retries.
  4. The payment settles on Base, and the analysis comes back with a _payment receipt (transaction hash, payer, network).

Limits

  • The output is analytics and decision support, not investment advice. It does not execute any payment.
  • It only analyses the data you supply. It does not fetch market data.
  • The HTTP API is also callable directly. Its OpenAPI spec is at /openapi.yaml and /openapi.json.

Source: README.md at commit eadde81

Tools

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

Version history

3
  1. v0.1.2LatestNov 3, 2026
  2. v0.1.1Nov 1, 2026
  3. v0.1.0Nov 1, 2026

Score

50% 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