Skip to content

Sentralis Portfolio Risk

by sentralis.io · remote · no sign-in to list tools · v1.0.0 · published by io.sentralis

Crypto portfolio risk analysis: VaR, scenarios, liquidity and correlation engines as MCP tools.

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http portfolio-risk https://app.sentralis.io/api/mcp --header 'Authorization: <your-authorization>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • run_risk_analysisSubmit a risk analysis (engines: monte-carlo, historical-replay, sector-concentration-stress, liquidity-stress, correlation-regime-stress, counterparty-infrastructure-risk, factor-…No findings

    Why it is in this group

    • The name "run_risk_analysis" says "run": a word for a change.
    Description, as the server wrote it
    Submit a risk analysis (engines: monte-carlo, historical-replay, sector-concentration-stress, liquidity-stress, correlation-regime-stress, counterparty-infrastructure-risk, factor-shock, macro-sensitivity). Provide EXACTLY ONE portfolio source: portfolio_ref (a stored portfolio id — see the user's portfolios) OR inline_positions (ad-hoc, max 30 positions of {symbol, amount-as-decimal-string}). config must satisfy the engine's JSON Schema from list_risk_engines. as_of_date (YYYY-MM-DD, engines with asOfDateSupported only) runs the analysis point-in-time: current portfolio composition × historical market data. ALWAYS returns an analysis_id immediately — poll get_analysis_result until status is succeeded or failed.
Only reads 3Claude Code: allow
  • get_analysis_resultFetch an analysis by id.No findings

    Why it is in this group

    • The name "get_analysis_result" says "get": a word for reading.
    Description, as the server wrote it
    Fetch an analysis by id. status=queued → poll again shortly; succeeded → result contains the risk envelope ({ok:true, result} or a persisted domain error like INSUFFICIENT_DATA) plus resolved data dates and the deterministic inputs hash; failed → error explains why.
  • list_risk_enginesList the available risk-analysis engines with their JSON-Schema config contracts, limits, and asOfDate (point-in-time) support.No findings

    Why it is in this group

    • The name "list_risk_engines" says "list": a word for reading.
    Description, as the server wrote it
    List the available risk-analysis engines with their JSON-Schema config contracts, limits, and asOfDate (point-in-time) support. Call this before run_risk_analysis to learn the exact config fields each engine requires.
  • list_supported_symbolsSearch the supported asset universe (max 100 results).No findings

    Why it is in this group

    • The name "list_supported_symbols" says "list": a word for reading.
    Description, as the server wrote it
    Search the supported asset universe (max 100 results). Preflight inline-portfolio symbols here — unknown symbols are dropped from valuation or yield INSUFFICIENT_DATA.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http portfolio-risk https://app.sentralis.io/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__portfolio-risk__list_risk_engines",
      "mcp__portfolio-risk__list_supported_symbols",
      "mcp__portfolio-risk__get_analysis_result"
    ],
    "ask": [
      "mcp__portfolio-risk__run_risk_analysis"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as portfolio-risk. Review it before you use it.