# veto (oci · ghcr.io/aiveto/veto)

Turn OpenAPI services into tools an agent can call under your rules.

- Trust score: 7/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- oci · `ghcr.io/aiveto/veto`: 7/100 (this document), [markdown](https://verifymcp.io/servers/aiveto-veto/ghcr-io-aiveto-veto.md), [page](https://verifymcp.io/servers/aiveto-veto/ghcr-io-aiveto-veto)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/aiveto/veto`
- Version: `0.1.13`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-19.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the veto MCP server?

veto runs locally as a container image, launched with docker run --rm -i ghcr.io/aiveto/veto:0.1.13. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add aiveto-veto -- docker run --rm -i ghcr.io/aiveto/veto:0.1.13
```

### Cursor

```json
{
  "mcpServers": {
    "aiveto-veto": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/aiveto/veto:0.1.13"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aiveto-veto": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/aiveto/veto:0.1.13"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add aiveto-veto -- docker run --rm -i ghcr.io/aiveto/veto:0.1.13
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aiveto-veto": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/aiveto/veto:0.1.13"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  aiveto-veto:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/aiveto/veto:0.1.13"]
```

### Netclaw

```json
{
  "McpServers": {
    "aiveto-veto": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/aiveto/veto:0.1.13"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "aiveto-veto": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/aiveto/veto:0.1.13"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-14 (score 7, 0)

- [security] Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.

### 2026-10-13 (score 7, 0)

- [functional] Package version: 0.1.12 → 0.1.13

### 2026-10-09 (score 7, 0)

- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.1.8 → 0.1.12

### 2026-10-08 (score 7, 0)

- [security] Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- [functional] Package version: 0.1.7 → 0.1.8

### 2026-10-04 (score 7, 0)

- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.1.4 → 0.1.7
- [functional] Package version: 0.1.4 → 0.1.6
- [functional] Package version: 0.1.4 → 0.1.5

### 2026-10-03 (score 7)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/aiveto-veto/ghcr-io-aiveto-veto#diagnostics

## Score history

- 2026-10-19: 7
- 2026-10-18: 7
- 2026-10-17: 7
- 2026-10-16: 7
- 2026-10-15: 7
- 2026-10-14: 7
- 2026-10-13: 7
- 2026-10-12: 7
- 2026-10-10: 7
- 2026-10-09: 7
- 2026-10-08: 7
- 2026-10-04: 7
- 2026-10-03: 7

## Common questions

### What is the veto MCP server?

veto is an MCP server listed in the public MCP registry as io.github.aiveto/veto. Turn OpenAPI services into tools an agent can call under your rules. This page covers its container image (ghcr.io/aiveto/veto).

### Is the veto MCP server safe to use?

veto scores 7 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Is the veto MCP server still maintained?

veto is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/aiveto/veto
- Repository: https://github.com/aiveto/veto
- Changelog RSS feed: https://verifymcp.io/servers/aiveto-veto/ghcr-io-aiveto-veto.xml
- Changelog JSON feed: https://verifymcp.io/servers/aiveto-veto/ghcr-io-aiveto-veto.json
- HTML version of this page: https://verifymcp.io/servers/aiveto-veto/ghcr-io-aiveto-veto