io.github.jackson-cmd/risk-aware-trading-agents
Risk-Aware Trading Agents
Is the Risk-Aware Trading Agents MCP server down? It gave no valid answer in the probe of 2026-11-14: not found. One failed probe is not an outage.
AI trading agents for US stocks: point-in-time news backtests, a frozen 2026 market, paper trading
not found no valid answer since 2026-11-14 · probed 2026-11-14
error: No solution found when resolving dependencies cause: Because there is no version of risk-aware-trading-agents==0.7.2 and you require risk-aware-trading
- Run it
- uvx risk-aware-trading-agents@0.7.2 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/jackson-cmd/risk-aware-trading-agents
- Website
- https://jackson-cmd.github.io/risk-aware-trading-agents/
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- MTG MCP Server io.github.j4th/mtg-mcp-server · crashed on start
- dep-rank io.github.j7an/dep-rank · needs args
- io.github.j7an/nexus-mcp · alive
- Aruba Email & Calendar io.github.jackfioru92/aruba-email · needs mcp<2
- ZEUS Terminal io.github.jackson-cmd/zeus-options-terminal · not probed
- io.github.jadenpxrk/mcp-piazza · alive
- Nexus-MCP io.github.jaggernaut007/nexus-mcp · alive
- memo io.github.jagoff/memo · crashed on start
Servers that mention trading.
- agency.lona/trading · needs auth
- ai.agentberg/agentberg · alive
- DJZS Trust MCP ai.djzs/trust-mcp · alive
- ai.firmbrain/x402-services · not found
- ai.iturri/market-data · alive
- Lattiq x402 Trading Signals ai.lattiq/x402-trading-signals · no DNS
- ai.quantifyme/quantifyme · alive
- RiskState — Crypto Risk Engine ai.riskstate/mcp · 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 package did not start as an MCP server at its probe on 2026-11-14. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.