io.github.vighriday/veris

Is the io.github.vighriday/veris MCP server down? Yes. It has given no valid answer since 2026-10-17: crashed on start.

Behavioral verification intelligence for AI coding agents. 17 MCP tools. Local-first. MIT.

crashed on start down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31

MCP error -32000: Connection closed
Error: ENOENT: no such file or directory, mkdir '/work/.veris'
  syscall: 'mkdir',
  path: '/work/.veris'
}
Node.js v22.23.5

Run it: npx -y veris-core@2.1.8 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/vighriday/Veris
Registry: active, updated 2026-05-18 · registry entry

Compare this server with others.

More servers

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

Spill io.github.vicc/spill · alive
io.github.videreo/collabsmap · crashed on start
DWIN Research Adoption io.github.vidvinianinov/dwin-research-adoption · alive
MainframeKit io.github.vidyutsaha1210/mainframekit · alive
io.github.vigneshRN52/demo-mcp-server · crashed on start
Invoice Studio io.github.vijayst/invoice-studio · alive
Aletheia Runtime Safety & Scope Creep Filter io.github.vikasny30/aletheia-mcp · alive
Switzerland MCP 🇨🇭 io.github.vikramgorla/swiss · alive

Servers that mention veris.

com.verisgov.api/data-access · alive
QVeris io.github.QVerisAI/mcp · needs auth
io.github.johnsmalls22-rgb/domain-search-king-mcp · alive
Averis Protocol io.github.mosaro0224/averis-protocol · not found
io.github.sercanmetalore/social-media-data-mcp · not found
io.github.veriswarm/veriswarm-mcp · alive
io.github.jakeyoung1/veris · alive
mcp-turkiye io.github.BerkantACUN/mcp-turkiye · 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.

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-17, in every probe since then.
The process exited on start before it answered initialize. The error output is above.