io.github.ipezygj/evalgate
io.github.ipezygj/evalgate
Is the io.github.ipezygj/evalgate MCP server down? Yes. It has given no valid answer since 2026-10-19: not found.
Statistical checks an agent runs before trusting an AI eval number (is #1 real, judge bias, more).
not found down since 2026-10-19 · probed 2026-11-14 · unchanged since 2026-10-26
error: No solution found when resolving dependencies cause: Because there is no version of eval-integrity==0.4.1 and you require eval-integrity==0.4.1, we can
- Run it
- uvx eval-integrity@0.4.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/ipezygj/evalgate
- Registry
- active, updated 2026-07-23 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- CLIO Web io.github.iowarp/web-mcp · needs network
- 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/numguard · 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
Servers that mention evalgate or statistical or trusting.
- EvalGate com.evalgate/evalgate · alive
- EvalGate Docs com.evalgate/evalgate-docs · alive
- ENYAL by Greenland AI ai.enyal/enyal · alive
- MCP Analytics ai.mcpanalytics/analytics · alive
- ai.smithery/turnono-datacommons-mcp-server · not found
- Disco com.leap-labs/discovery-engine · alive
- MCPFax Macro & Market Intelligence com.mcpscores/macro-market-data · alive
- Scientific Microservices com.scientificmicroservices/mcp · 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.
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-19, 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.