Protocol Wealth · Open Source

Nexus Core

A regime-adaptive financial analysis engine, exposed as a public API and as Model Context Protocol (MCP) tools. Market data, macro signals, options, DeFi analytics, and PII-free planning math. Native MCP can run as a public demo endpoint; production REST/JSON calculation paths can require a service API key. Remote MCP clients may complete transparent OAuth with no login.

MCP setup guide →

Connect Claude Desktop or any MCP client — hosted or local

API documentation →

Interactive OpenAPI / Swagger explorer

Restricted REST API →

Service-key calculation endpoints for trusted callers

Source on GitHub →

Apache-2.0 — fork it, run it, extend it

OpenAPI schema →

Machine-readable API contract

Endpoints

GET /api/regime — current macro regime classification
GET /api/regime/signals — raw regime signal readings
GET /api/market/quote/{symbol} — latest quote (stocks, ETFs, indices, crypto)
GET /api/market/history/{symbol} — OHLCV price history
GET /api/economic/{series_id} — FRED economic series
POST /mcp — Model Context Protocol endpoint (connect any MCP-compatible AI client — setup guide)

Try it

# current macro regime
curl https://nexusmcp.site/health
curl -H "Authorization: Bearer $NEXUS_SERVICE_API_KEY" \
  https://nexusmcp.site/api/regime

# planning tools: contract handshake, then invoke one (educational, PII-free)
curl -H "Authorization: Bearer $NEXUS_SERVICE_API_KEY" \
  https://nexusmcp.site/api/planning/tools
curl -X POST https://nexusmcp.site/api/planning/tools/glide_path \
  -H "Authorization: Bearer $NEXUS_SERVICE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"currentAge": 40, "retirementAge": 65, "horizonAge": 95, "startEquityWeight": 0.8, "endEquityWeight": 0.4, "shape": "linear"}'

Public surface only

Native MCP can remain an OAuth-compatible public demo surface; hosted REST/JSON calculation endpoints require a trusted service key. This deployment contains no client data, no account surfaces, no suitability logic, no report production workflow, and no advisory workflow state — those live in Protocol Wealth's closed systems. Planning endpoints accept de-identified inputs only.