ai.fortunest/portfolio
Fortunest
Is the Fortunest MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-10.
Ask about your real portfolio: holdings, risk, tax lots and trades across brokers and exchanges.
needs auth probed 2026-11-15 · unchanged since 2026-11-10 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error": "invalid_token", "error_description": "Authentication required"}- Endpoint
- https://app.fortunest.ai/mcp (streamable-http)
- Host
- app.fortunest.ai
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.fortunest.ai/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server app.fortunest.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes assistant:spend connectors:sync context:read dashboard:control dashboard:read memory:write notes:write portfolio:read portfolio:write settings:write social:read social:write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/jstrunc/fortunest-mcp
- Website
- https://fortunest.ai/docs/mcp.html?utm_source=mcp-registry&utm_medium=directory&utm_campaign=mcp-listing
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Other registry entries on app.fortunest.ai.
- Fortunest demo ai.fortunest/portfolio-demo · alive
Servers that mention portfolio.
- agency.lona/trading · needs auth
- Rayana AI ai.rayana/rayana-ai · alive
- Stonewake ai.stonewake/stonewake · alive
- Bonsave app.bonsave/bonsave · needs auth
- HADL — портфельный трекер app.hadl/portfolio · needs auth
- Manawa Terminal app.manawa/manawa-terminal · alive
- Worthbase app.worthbase/worthbase · needs auth
- ar.com.sofiaferro/portfolio · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.