io.github.ipezygj/numguard
io.github.ipezygj/numguard
Is the io.github.ipezygj/numguard MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.
Verify a number before an agent asserts it — evals, backtests (Deflated Sharpe), signed receipts.
not found down since 2026-10-18 · probed 2026-11-14 · unchanged since 2026-11-01
error: No solution found when resolving dependencies cause: Because there is no version of numguard==0.1.1 and you require numguard==0.1.1, we can conclude th
- Run it
- uvx numguard@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/ipezygj/numguard
- Registry
- active, updated 2026-07-24 · 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.ip2location/mcp-ip2location-io · needs mcp<2
- io.github.ip2whois/mcp-ip2whois · needs mcp<2
- io.github.ipezygj/agent-guard · not found
- io.github.ipezygj/evalgate · not found
- Bing Search (Free) io.github.iridite/bing-search-free · timeout
- MemoryGuard io.github.irisxc4/memoryguard · needs args
- Code of Paper io.github.isagelswann/codeofpaper · crashed on start
- Weather MCP Server io.github.isdaniel/mcp_weather_server · crashed on start
Servers that mention backtests or deflated.
- TraderSpy app.traderspy/traderspy · alive
- com.alphaassay/mcp · alive
- DCA Method — backtests & calculators com.dcamethod/dca-tools · alive
- HaasOnline Trade Server com.haasonline/trade-server · needs auth
- Papers With Backtest com.paperswithbacktest/papers-with-backtest · needs auth
- Quantradin com.quantradin/quantradin · needs auth
- Sentinel Aleph com.ribqa/sentinel-aleph · alive
- TradeAssi com.tradeassi/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
- No valid answer since 2026-10-18, in every probe since then.
- 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.