MCP server health, State of MCP census
QuantRisk
dev.quantrisk/mcp-server
Portfolio risk analytics — VaR, Monte Carlo, optimization, options Greeks, stress testing.
Checks
The exact rows akashi check dev.quantrisk/mcp-server prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | pass | exists |
| repo freshness | pass | pushed 36d ago |
| package npm | pass | published (1.0.3) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 10 tools: analyze_risk, monte_carlo_simulation, stress_test, optimize_portfolio, correlation_matrix, performance_attribution, sector_exposure, price_history, ... |
| at least one live entrypoint | pass | 3 alive |
| license present | pass | MIT |
Evidence
Packages
- npm @quantrisk/mcp-server · published(1.0.3)
Remote endpoints
- https://quantrisk-mcp.quantrisk.workers.dev/mcp
streamable-http · reachable· HTTP 200· initialize_ok
10 tools: analyze_risk, monte_carlo_simulation, stress_test, optimize_portfolio, correlation_matrix, performance_attribution, sector_exposure, price_history, ...
server.json
validagainst its declared schema
One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check dev.quantrisk/mcp-serverInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check dev.quantrisk/mcp-server --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.