io.github.clm-studios/nephyr-backtest

Nephyr Backtest

Is the Nephyr Backtest MCP server down? Yes. It has given no valid answer since 2026-10-18: crashed on start.

Prediction market strategy backtesting with real on-chain Polymarket data

crashed on start down since 2026-10-18 · probed 2026-11-14 · unchanged since 2026-11-01

MCP error -32000: Connection closed
ModuleNotFoundError: No module named 'mcp_server'
Traceback (most recent call last):
  File "/work/bin/nephyr-backtest-mcp",

Run it: uvx nephyr-backtest@0.1.1 (stdio, probed in a container with the network off)
Host: pypi.org
Repository: https://github.com/clm-studios/nephyr-backtest
Registry: active, updated 2026-04-01 · registry entry

Compare this server with others.

More servers

Other registry entries on pypi.org, the ones next to this name; all of them.

io.github.clarenceh/expenselm-mcp-server · alive
Clay Seal io.github.clayseal/clayseal · crashed on start
SAM.gov Opportunities io.github.clean-data-labs-org/samgov-opportunities · alive
Avrotize io.github.clemensv/avrotize · crashed on start
Nephyr Risk io.github.clm-studios/nephyr-risk · crashed on start
Nephyr Wallets io.github.clm-studios/nephyr-wallets · crashed on start
Nephyr Weather io.github.clm-studios/nephyr-weather · crashed on start
cloudcostwise io.github.cloudwise-app/cloudcostwise · alive

Servers that mention backtest.

agency.lona/trading · needs auth
ai.avasis/quant-research · needs auth
ai.tessen/grader · not found
AI Backtester app.aibacktester/aibacktester · needs auth
TraderSpy app.traderspy/traderspy · alive
com.alphaassay/mcp · alive
Backtest360 com.backtest360/backtest360 · server error
CPZAI com.cpz-lab.mcp/cpzai · needs auth

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.

Atom feed

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

No valid answer since 2026-10-18, in every probe since then.
The process exited on start before it answered initialize. The error output is above.