Skip to content

Sentralis Portfolio Risk MCP server

io.sentralis/portfolio-risksentralis.iostreamable-httpv1.0.0Scanned

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

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Sentralis Portfolio Risk MCP server can do

The Sentralis Portfolio Risk MCP server is published by sentralis.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: run_risk_analysis), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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 3Show 3 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.sentralis.io/api/mcp: tools/list returned 4 tools to an anonymous client, including run_risk_analysis (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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>'
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as portfolio-risk. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.sentralis/portfolio-risk/verify?hash=3239ec3eb62a150958d1a5471be38098c6de5e53ece95fbf0be30a94cde6da52" | jq -e '.changed == false'

Pinned hash 3239ec3eb62a, from Nov 18, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.sentralis/portfolio-risk/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.sentralis/portfolio-risk
[![Anlyon Radar](https://radar.anlyon.com/badge/io.sentralis/portfolio-risk.svg)](https://radar.anlyon.com/servers/io.sentralis/portfolio-risk)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.

Sentralis Portfolio Risk MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Sentralis Portfolio Risk MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Sentralis Portfolio Risk MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Sentralis Portfolio Risk MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Sentralis Portfolio Risk MCP server have?

4 tools: 1 write, 3 read. run_risk_analysis, list_risk_engines, list_supported_symbols and get_analysis_result.

Does the Sentralis Portfolio Risk MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Sentralis Portfolio Risk MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Sentralis Portfolio Risk MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.