io.github.veto-protocol/mcp

Is the io.github.veto-protocol/mcp MCP server down? It gave no valid answer in the probe of 2026-11-10: crashed on start. One failed probe is not an outage.

Agentic checkout for Veto merchants: discover, search, quote, pay, and verify signed receipts.

crashed on start no valid answer since 2026-11-10 · probed 2026-11-14 · unchanged since 2026-11-10

MCP error -32000: Connection closed
Error [ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING]: Stripping types is currently unsupported for files under node_modules,

Run it: npx -y @veto-protocol/mcp@0.1.1 (stdio, probed in a container with the network off)
Host: npmjs.com
Website: https://merchants.veto-ai.com
Registry: active, updated 2026-11-09 · registry entry

Compare this server with others.

More servers

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

MCP FreeScout io.github.verygoodplugins/mcp-freescout · alive
MCP Local WP io.github.verygoodplugins/mcp-local-wp · alive
MCP Pirsch io.github.verygoodplugins/mcp-pirsch · alive
io.github.vessel-api/vesselapi-mcp · alive
Agent Release Auditor io.github.veyndrasystems/agent-release-auditor · needs args
io.github.vfa-khuongdv/mcp-backlog · alive
io.github.vfa-khuongdv/redmine · alive
io.github.vfarcic/dot-ai · needs env

Servers that mention veto.

Gigi AI ai.usegigi/gigi · needs auth
Verificate MCP ai.verificate/mcp · alive
cc.ticktape/mcp · alive
Veto — SQL Safety & Cost Oracle com.vetosql/veto · alive
Chapa io.github.juan294/chapa · alive
4D Results (Malaysia, Singapore, Cambodia) io.github.oddsflowai-team/4dlivetoday · alive
Vetofix – Hilfe zur Praxissoftware für Tierarzt-Hausbesuche com.vetofix/hilfe · alive
Delve to Life com.delvetolife.mcp/delve-to-life · 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

The package did not start as an MCP server at its probe on 2026-11-10. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
The process exited on start before it answered initialize. The error output is above.