com.xtrinel/vaast

Is the com.xtrinel/vaast MCP server down? Yes. It has given no valid answer since 2026-10-18: crashed on start.

Read-only access to VAAST vulnerability scan findings, workspaces, and targets for AI agents

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

MCP error -32000: Connection closed
Fatal error: Failed to read VAAST MCP session file at /root/.vaast/mcp.json. Make sure VAAST is running and the MCP server i

Run it: npx -y @xtrinel/vaast-mcp@0.1.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Registry: active, updated 2026-10-02 · registry entry
Changes: 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.

Compare this server with others.

More servers

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

com.xcodebuildmcp/XcodeBuildMCP · crashed on start
XCREENER com.xcreener/xcreener-mcp · alive
XPmetric com.xpmetric/mcp · alive
xStocker com.xstocker/agent-mcp · alive
com.yaktool/compliance · alive
com.yaktool/gs1 · alive
com.yaktool/image · alive
com.yaktool/invoice · alive

Servers that mention vulnerability or workspaces.

Filepad ai.filepad/filepad · server error
ai.plori/plori · needs auth
Kanera app.kanera/mcp · needs auth
Priorify app.priorify/priorify · needs auth
ai.smithery/smithery-ai-slack · not found
Trilo chat.trilo/mcp · needs auth
AcornReply com.acornreply/server · needs auth
CERT-FR Security Advisories — buy per-query in-session (certfrwatch) com.a2awire/data-cert-fr-advisory-national-cert-alert · alive

History

We add a row when the result changes. A server with no change keeps its last row.

Probed	Result	Init	Tools	Claude	o200k
2026-11-01 08:10	crashed on start
2026-10-18 06:38	not MCP

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.