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.

Treasury Risk Analyzer

NPM · TREASURY-RISK-MCP

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

Available components

67 Trust /100

Last scanned (5 hours ago)

Scores higher than 35% of npm servers

Category Finance and Payments

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 Security99
  • 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
  • 30 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1417 tokens (~202/item across 7 items; 7 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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.

  • 3 Nov 26 +1
    • Package version: 0.1.1 → 0.1.2 functional
  • 2 Nov 26 +1

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

  • 1 Nov 26 65

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/treasury-risk-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 npm

Background: How many MCP packages publish verified provenance →

Dependencies 111 packages
Packages resolved 111
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,417 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
describe_service ~59

Free. Describes the Treasury Risk Analyzer (deterministic treasury risk, FX exposure, liquidity and payment-decision analytics for AI Treasury/CFO agents), lists the paid tools with their USDC prices, and reports whether this server is configured to pay.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fx_exposure ~212

PAID: $0.25 USDC per call on Base (x402), charged only for valid input. Deterministic FX exposure analysis. Computes gross/net exposure, currency concentration, natural hedges, stress scenarios, and hedge priority from a list of receivable/ payable/cash positions by currency. Requires USDC payment via the x402 protocol (Circle Gateway) — see the 402 response for the payment flow. All figures are computed deterministically (no LLM). Call get_example_input first if unsure of the shape.

NameTypeReqDescription
baseCurrencystring––
fxRatesobjectyesUnits of baseCurrency per 1 unit of each foreign currency present in `positions`.
positionsarrayyes–
stressShockPctnumber–Fractional depreciation applied to each foreign currency in the stress scenario.
totalTreasuryValueBasenumber–Optional total treasury value (in baseCurrency) used to normalize the risk score. Defaults to total gross FX exposure if omitted.

No output schema declared.

No examples provided.

get_example_input ~41

Free. Returns a valid example input for one of the paid tools — a quick way to learn the expected shape before paying.

NameTypeReqDescription
toolstringyes–

No output schema declared.

No examples provided.

liquidity_forecast ~271

PAID: $0.50 USDC per call on Base (x402), charged only for valid input. Deterministic liquidity forecast. Projects daily cash balance from opening cash and a list of scheduled cash flow events over a forecast horizon, flags minimum-buffer breaches, and classifies liquidity status. Optionally also computes standard working-capital ratios (DSO/DPO/DIO/cash conversion cycle) from a supplied balance snapshot. Requires USDC payment via the x402 protocol (Circle Gateway) — see the 402 response for the payment flow. All figures are computed deterministically (no LLM). Call get_example_input first if unsure of the shape.

NameTypeReqDescription
baseCurrencystring––
cashFlowsarray–Each date must be on or after startDate; dates beyond the horizon are excluded from the projection (and flagged in warnings/data_quality) rather than rejected.
horizonDaysintegeryes–
minimumCashBuffernumberyes–
openingCashnumberyes–
startDatestring–Defaults to today (UTC) if omitted.
workingCapitalobject–Optional standard accounting ratios (DSO/DPO/DIO/cash conversion cycle) computed from a balance snapshot and period flow — independent of the cashFlows-based daily projection above.

No output schema declared.

No examples provided.

run_demo ~93

Free. Runs one of the paid tools on fixed sample data and returns its real, full output, so you can see exactly what the paid tool returns before paying. Default: treasury_decision on a EUR 750,000 supplier invoice ("can we pay it today?"). Does not accept your own data — use the paid tool for that. Limited to about 20 calls per hour.

NameTypeReqDescription
toolstring––

No output schema declared.

No examples provided.

treasury_decision ~276

PAID: $2.00 USDC per call on Base (x402), charged only for valid input. Composite payment decision ("can we safely execute this payment today?"). Orchestrates the liquidity, FX exposure, and (optionally) treasury risk capabilities to produce a PAY/REVIEW/DO_NOT_PAY decision with a confidence score. The payment is injected as an outflow into the liquidity forecast and as a new unhedged payable position in the FX exposure analysis. Requires USDC payment via the x402 protocol (Circle Gateway) — see the 402 response for the payment flow. This is decision-support output, not an instruction to execute any transaction. All figures are computed deterministically (no LLM). Call get_example_input first if unsure of the shape.

NameTypeReqDescription
baseCurrencystring––
fxExposureobjectyesSame shape as the /fx-exposure request body minus baseCurrency; positions is optional (the payment is auto-injected as a new unhedged payable position). fxRates must include the payment currency's ra…
liquidityobjectyesSame shape as LiquidityRequest, minus baseCurrency (the payment is auto-injected as an additional cash flow outflow).
paymentobjectyes–
treasuryRiskobject––

No output schema declared.

No examples provided.

treasury_risk ~465

PAID: $0.10 USDC per call on Base (x402), charged only for valid input. Deterministic treasury/portfolio risk analysis. Computes volatility, Sharpe/Sortino/Calmar, VaR/Expected Shortfall, multi-dimensional concentration, per-asset risk contribution, and correlated multi-factor stress scenarios (shocks propagate to unshocked symbols via covariance-based beta mapping, not treated as zero) from historical per-period returns and portfolio weights. Requires USDC payment via the x402 protocol (Circle Gateway) — see the 402 response below for the payment flow. Also available at the legacy path POST /analyze (identical behavior). All figures are computed deterministically (no LLM). Call get_example_input first if unsure of the shape.

NameTypeReqDescription
baseCurrencystring––
benchmarkReturnsarray–Optional per-period benchmark series (same length as each `returns` series) to compute beta and correlation.
confidenceLevelsarray–Confidence levels for VaR/Expected Shortfall. Supported: 0.9, 0.95, 0.975, 0.99, 0.995.
currencyExposureobject–Optional weight distribution by currency, for concentration analysis.
geographyExposureobject–Optional weight distribution by geography, for concentration analysis.
minimumAcceptableReturnnumber–Per-period MAR used for downside deviation / Sortino ratio.
periodsPerYearnumber–Periods per year in the return series (252 for daily equities, 365 for daily crypto).
returnsobjectyesPer-period historical return series by symbol. All series must be the same length (≥2 observations).
riskFreeRatenumber–Annualized risk-free rate, e.g. 0.04 for 4%.
sectorExposureobject–Optional weight distribution by sector, for concentration analysis.
stressScenariosarray–Optional stress scenarios. Shocks on the listed symbols propagate to unshocked symbols via covariance-based beta mapping (correlated impact), alongside the direct-only impact.
weightsobjectyesPortfolio weights by symbol. Must cover exactly the same symbols as `returns` and sum to 1.

No output schema declared.

No examples provided.

Install

How do I install the Treasury Risk Analyzer MCP server?

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

npm · treasury-risk-mcp

# add to Claude Code
claude mcp add christianmatumona-treasury-risk-mcp -- npx -y treasury-risk-mcp
Common questions

What is the Treasury Risk Analyzer MCP server?

Treasury Risk Analyzer is an MCP server listed in the public MCP registry as io.github.christianmatumona/treasury-risk-mcp. Treasury risk, FX exposure, liquidity & payment decisions for AI CFO agents. Pay per call in USDC. This page covers its npm package (treasury-risk-mcp).

Is the Treasury Risk Analyzer MCP server safe to use?

Treasury Risk Analyzer scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Treasury Risk Analyzer MCP server expose?

Treasury Risk Analyzer exposes 7 tools: describe_service, get_example_input, run_demo, treasury_risk, fx_exposure, and 2 more. Their descriptions and schemas cost roughly 1,417 tokens of context every time the server is loaded.

Is the Treasury Risk Analyzer MCP server still maintained?

Treasury Risk Analyzer is still listed as active in the MCP registry. We last reached this channel on 5 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 Treasury Risk Analyzer MCP server under?

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