mcpbeat Sign in

Veto MCP Server

by jigyasudham Your server? Claim it
local only

Veto runs on your own machine — the client starts it, so there is no endpoint to ping. 239 installs a week from npm. Last commit 4 Oct 2026.

93 agentic MCP tools + 49 specialist agents for every major AI CLI. Self-learning, no API keys.

Installs per day peak 127 · avg 30 · -32% w/w
a month agotoday
239
Installs / week
npm · @jigyasudham/veto
4
Stars
0 open issues
4 Oct 2026
Last commit
14 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 2 d ago · rules 995398eba69f

A tool parameter reaches a dangerous call

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

A tool parameter reaches a dangerous call veto_handoff.project_dir → src/server/handlers/advisors.ts:284, veto_handoff.project_dir → src/server/handlers/advisors.ts:312, veto_handoff.project_dir → src/server/handlers/generators.ts:175 и ещё 26
        const candidates = execSync(
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    return execSync(cmd, { windowsHide: true, cwd, timeout: 3000, stdio: ['pipe', 'pipe', 'pipe'] }).toString().trim();
Touches key and credential files src/agents/security/secrets.ts:56
      'Checking in AWS credentials profile files (~/.aws/credentials) via CI runners',

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

A tool parameter here reaches a dangerous call

That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add veto -- npx -y @jigyasudham/veto
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "veto": {
      "command": "npx",
      "args": [
        "-y",
        "@jigyasudham/veto"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.veto]
command = "npx"
args = ["-y", "@jigyasudham/veto"]
.cursor/mcp.json
{
  "mcpServers": {
    "veto": {
      "command": "npx",
      "args": [
        "-y",
        "@jigyasudham/veto"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "veto": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@jigyasudham/veto"
      ]
    }
  }
}

Alternatives to Veto

same job, measured the same way
ToolAPI
by toolapi

Free public MCP for AI agents — 193 tools, 44 workflows. No API key.

193 tools answering
Sub Agents MCP
by shinpr

MCP server for delegating tasks to specialized AI sub-agents across coding tools

230 installs/wk local only
Tdai Memory MCP
by tinhien11

Local-first MCP memory server for coding agents. No API key, no cloud. SQLite + FTS5 + sqlite-vec.

85 installs/wk local only
Untappd
by darrenjrobinson

MCP server exposing Untappd API tools for AI agents — full v4 read API coverage

80 installs/wk local only
Looking Glass MCP
by sahib-sawhney-wh

AI-native browser for agents. 71 tools with self-healing, semantic extraction, vault CLI.

67 installs/wk local only
Keyblind
by aarifmms

Encrypted secrets vault for AI agents. 27 MCP tools resolve secrets at runtime, never leaking them.

263 installs/wk local only
ToolSnap MCP
by toolsnap

Deterministic AI agent microtools, no accounts/API keys. fetch_extract: 98% token cut. 47 tools.

17 tools answering
Yourimageshare
by yourimageshare

MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.

68 installs/wk 5 tools answering

Veto — questions

Answers built from our own checks of this server.

Why is there no uptime for Veto?
Veto runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @jigyasudham/veto was installed 239 times last week.
How do I connect Veto?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @jigyasudham/veto straight from npm; nothing to host, nothing to sign up for.
How many people use Veto?
The npm package @jigyasudham/veto was installed 239 times in the last week. Week over week that is -32%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Veto open source?
Yes — it is published under the MIT licence, written in TypeScript and 4 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.