Sentralis Portfolio Risk

io.sentralisPublished by sentralis.ioOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote MCP server that runs crypto portfolio risk analysis — VaR, stress scenarios, liquidity and correlation engines — and returns results by analysis id.

What you can do
List available risk engines with their JSON-Schema config contracts, limits and point-in-time support, and search the supported asset universe to preflight symbols before analysis (max 100 results). Submit a risk analysis using exactly one portfolio source, choosing among engines such as Monte Carlo, historical replay, sector-concentration, liquidity, correlation-regime, counterparty-infrastructure, factor-shock and macro-sensitivity. Fetch an analysis by id, polling while queued and reading the risk envelope, resolved data dates and deterministic inputs hash once it succeeds.
When to use it
Useful when an assistant needs quantitative crypto portfolio risk figures — value-at-risk, stress scenarios, liquidity or correlation exposure — rather than raw market data, and when results should be reproducible via a stored portfolio and inputs hash.
Requirements
A remote endpoint at app.sentralis.io over streamable HTTP. A bearer API key is required in the Authorization header; keys are generated under API Keys after creating a free account. No local runtime or environment variables are declared.
Before you install
The Authorization header carries a live API key (sk_live_ prefix) and must be kept secret. Analyses are submitted to a third-party service and may consume account quota or credits; check plan limits before running large jobs. Portfolio data is sent to that service.

Installation

In SourceWeft

  1. Open Sentralis Portfolio Risk in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.sentralis%2Fportfolio-risk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sentralis-portfolio-risk": {
      "type": "http",
      "url": "https://app.sentralis.io/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

4

list_risk_engines

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.

Takes no parameters.

list_supported_symbols

Search the supported asset universe (max 100 results). Preflight inline-portfolio symbols here — unknown symbols are dropped from valuation or yield INSUFFICIENT_DATA.

Parametersquery

run_risk_analysis

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.

Parametersconfigrequiredenginerequiredas_of_dateportfolio_refinline_positions

get_analysis_result

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.

Parametersanalysis_idrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.