sentralis-portfolio-risk
Registry code: aa0cb6f1e616aca2
Crypto portfolio risk analysis: VaR, scenarios, liquidity and correlation engines as MCP tools.
from a public catalogue that lists it, not from the operator
- endpoint
- https://app.sentralis.io/api/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is sentralis-portfolio-risk live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is sentralis-portfolio-risk free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does sentralis-portfolio-risk have?
- 4 tools: list_risk_engines, list_supported_symbols, run_risk_analysis, get_analysis_result.
- Is sentralis-portfolio-risk safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_risk_engines auth-required 1h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 lineslist_supported_symbols auth-required 1h ago
Search the supported asset universe (max 100 results). Preflight inline-portfolio symbols here — unknown symbols are dropped from valuation or yield INSUFFICIENT_DATA.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "query": { "type": "string", "maxLength": 40 } }, "additionalProperties": false }arguments 11 linesrun_risk_analysis auth-required never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "engine", "config" ], "properties": { "config": { "type": "object", "additionalProperties": {} }, "engine": { "enum": [ "monte-carlo", "historical-replay", "sector-concentration-stress", "liquidity-stress", "correlation-regime-stress", "counterparty-infrastructure-risk", "factor-shock", "macro-sensitivity" ], "type": "string" }, "as_of_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$" }, "portfolio_ref": { "type": "string", "maxLength": 100 }, "inline_positions": { "type": "array", "items": { "type": "object", "required": [ "symbol", "amount" ], "properties": { "amount": { "type": "string", "maxLength": 60, "minLength": 1 }, "symbol": { "type": "string", "maxLength": 40, "minLength": 1 } }, "additionalProperties": false }, "maxItems": 30, "minItems": 1 } }, "additionalProperties": false }arguments 61 linesget_analysis_result auth-required 1h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "analysis_id" ], "properties": { "analysis_id": { "type": "string", "format": "uuid" } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idaa0cb6f1e616aca2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa0cb6f1e616aca2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/aa0cb6f1e616aca2?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.