# Vericto Proxy mode (local, PostgreSQL) (oci · docker.io/vericto/vericto-proxy)

Read-only PostgreSQL for AI agents: every statement is checked before it runs. No account needed.

- Trust score: 22/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- oci · `docker.io/vericto/vericto-proxy`: 22/100 (this document), [markdown](https://verifymcp.io/servers/com-vericto-vericto-proxy/docker-io-vericto-vericto-proxy.md), [page](https://verifymcp.io/servers/com-vericto-vericto-proxy/docker-io-vericto-vericto-proxy)

## Channel facts

- Registry: `oci`
- Package: `docker.io/vericto/vericto-proxy`
- Version: `5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9`
- 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-11-06.

- **Supply Chain Security**: 8/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.
  - CVE check failed: a known advisory affects this package; its severity couldn't be graded.
  - 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**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to vericto/vericto-proxy).
  - Clear OSI-approved license (AGPL-3.0-only).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Vericto Proxy mode (local, PostgreSQL) MCP server?

Vericto Proxy mode (local, PostgreSQL) runs locally as a container image, launched with docker run --rm -i -e VERICTO_API_KEY -e VERICTO_DATABASE_ID docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9 /usr/local/bin/vericto-proxy mcp --database-url-file /run/secrets/db.url, plus the required --user and -v, which you supply. 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 com-vericto-vericto-proxy -- docker run --rm -i -e VERICTO_API_KEY -e VERICTO_DATABASE_ID docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9 /usr/local/bin/vericto-proxy mcp --database-url-file /run/secrets/db.url
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Cursor

```json
{
  "mcpServers": {
    "com-vericto-vericto-proxy": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "VERICTO_API_KEY",
        "-e",
        "VERICTO_DATABASE_ID",
        "docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9",
        "/usr/local/bin/vericto-proxy",
        "mcp",
        "--database-url-file",
        "/run/secrets/db.url"
      ]
    }
  }
}
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

### VS Code

```json
{
  "servers": {
    "com-vericto-vericto-proxy": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "VERICTO_API_KEY",
        "-e",
        "VERICTO_DATABASE_ID",
        "docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9",
        "/usr/local/bin/vericto-proxy",
        "mcp",
        "--database-url-file",
        "/run/secrets/db.url"
      ]
    }
  }
}
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Codex

```bash
codex mcp add com-vericto-vericto-proxy -- docker run --rm -i -e VERICTO_API_KEY -e VERICTO_DATABASE_ID docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9 /usr/local/bin/vericto-proxy mcp --database-url-file /run/secrets/db.url
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vericto-vericto-proxy": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "VERICTO_API_KEY",
        "-e",
        "VERICTO_DATABASE_ID",
        "docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9",
        "/usr/local/bin/vericto-proxy",
        "mcp",
        "--database-url-file",
        "/run/secrets/db.url"
      ],
      "enabled": true
    }
  }
}
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Hermes

```yaml
mcp_servers:
  com-vericto-vericto-proxy:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "VERICTO_API_KEY", "-e", "VERICTO_DATABASE_ID", "docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9", "/usr/local/bin/vericto-proxy", "mcp", "--database-url-file", "/run/secrets/db.url"]
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Netclaw

```json
{
  "McpServers": {
    "com-vericto-vericto-proxy": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "VERICTO_API_KEY",
        "-e",
        "VERICTO_DATABASE_ID",
        "docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9",
        "/usr/local/bin/vericto-proxy",
        "mcp",
        "--database-url-file",
        "/run/secrets/db.url"
      ]
    }
  }
}
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Other

```json
{
  "mcpServers": {
    "com-vericto-vericto-proxy": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "VERICTO_API_KEY",
        "-e",
        "VERICTO_DATABASE_ID",
        "docker.io/vericto/vericto-proxy:5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9",
        "/usr/local/bin/vericto-proxy",
        "mcp",
        "--database-url-file",
        "/run/secrets/db.url"
      ]
    }
  }
}
```

This image reads VERICTO_API_KEY and VERICTO_DATABASE_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --user and -v as required and gives no value we can show, so they are not in this command. Add them before you run it.

## 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-11-06 (score 22, −6)

- [security regression] CVE-2026-84243 affects this package: none
- [security regression] Known CVEs: pass → fail

### 2026-11-05 (score 28, +6)

- [security improvement] CVE-2026-97399 no longer affects this package
- [security improvement] CVE-2026-89092 no longer affects this package
- [security improvement] Known CVEs: fail → pass

### 2026-11-04 (score 22, +2)

- [functional improvement] License: fail → pass
- [functional] Licence: FSL-1.1-ALv2 → AGPL-3.0-only
- [functional] Package version: 4.23.0@sha256:c13b87f448548d6090d29462e75ca10551172a7b3d2cdd60fa408e0338e52e31 → 5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9

### 2026-11-01 (score 20)

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, Vulnerabilities. The full working is on the page: https://verifymcp.io/servers/com-vericto-vericto-proxy/docker-io-vericto-vericto-proxy#diagnostics

## Score history

- 2026-11-06: 22
- 2026-11-05: 28
- 2026-11-04: 22
- 2026-11-03: 20
- 2026-11-02: 20
- 2026-11-01: 20

## Common questions

### What is the Vericto Proxy mode (local, PostgreSQL) MCP server?

Vericto Proxy mode (local, PostgreSQL) is an MCP server listed in the public MCP registry as com.vericto/vericto-proxy. Read-only PostgreSQL for AI agents: every statement is checked before it runs. No account needed. This page covers its container image (docker.io/vericto/vericto-proxy).

### Is the Vericto Proxy mode (local, PostgreSQL) MCP server safe to use?

Vericto Proxy mode (local, PostgreSQL) scores 22 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 6 November 2026. Its build provenance is signed and verified. 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 Vericto Proxy mode (local, PostgreSQL) MCP server still maintained?

Vericto Proxy mode (local, PostgreSQL) is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Vericto Proxy mode (local, PostgreSQL) MCP server under?

Vericto Proxy mode (local, PostgreSQL) declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Vericto Proxy mode (local, PostgreSQL) MCP server?

VerifyMCP ran 6 checks on Vericto Proxy mode (local, PostgreSQL), covering Known CVEs, Source repository, Provenance, License and 2 more. 8 items could not be completed, a gap on our side rather than a finding about Vericto Proxy mode (local, PostgreSQL): Malware scan, Install scripts, Dependency health, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Docker Hub: https://hub.docker.com/r/vericto/vericto-proxy
- Repository: https://github.com/vericto/vericto-proxy
- Website: https://github.com/vericto/vericto-proxy/blob/main/docs/MCP.md
- Changelog RSS feed: https://verifymcp.io/servers/com-vericto-vericto-proxy/docker-io-vericto-vericto-proxy.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vericto-vericto-proxy/docker-io-vericto-vericto-proxy/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-vericto-vericto-proxy/docker-io-vericto-vericto-proxy.json
- HTML version of this page: https://verifymcp.io/servers/com-vericto-vericto-proxy/docker-io-vericto-vericto-proxy