io.github.baopeak/verirun
io.github.baopeak/verirun
Is the io.github.baopeak/verirun MCP server down? Yes. It has given no valid answer since 2026-10-16: install failed.
Execution-grounded verification for AI coding agents on Windows: evidence, not agent claims.
install failed down since 2026-10-16 · probed 2026-11-14 · unchanged since 2026-10-30
npm error notsup Valid os: win32 npm error notsup Actual os: linux npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-13T08_47_02_1
- Run it
- npx -y verirun@0.2.1-dev (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/baopeak/verirun
- Registry
- active, updated 2026-09-14 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Google Workspace (multi-account) io.github.bakissation/mcp-google-multi · needs env
- io.github.balt1794/alttextgeneratorai-mcp · alive
- io.github.bamwor-dev/bamwor-mcp-server · alive
- io.github.baodq06/memocall · alive
- io.github.barissozudogru/gha-intel · alive
- Release Intel io.github.barissozudogru/release-intel · alive
- Test Intel io.github.barissozudogru/test-intel · alive
- WebLens io.github.bartenderthiago82/weblens · needs env
Servers that mention verification or execution.
- ai.atlasverified/atlas-mcp · needs auth
- DeployIt Product Expert ai.deployit/product-expert · alive
- DJZS Trust MCP ai.djzs/trust-mcp · alive
- ai.facesign/facesign-mcp · alive
- Foliora Managed AI Search ai.foliora/search · needs auth
- ai.geodesiclabs/governance-platform · alive
- Human4AI Human Task Network ai.human4ai/collaboration · alive
- InfraPulse ai.infrapulse/infrapulse · rejects our protocol version
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-16, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.