Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

Available components

oci · docker.io/vericto/vericto-proxy 22
22 Trust /100

Last scanned (5 hours ago)

Scores higher than 36% of OCI servers

Category Databases

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security8
  • 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.Unverified
  • CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
  • Install-script risk not yet assessed.Unverified
  • 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.Unverified
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to vericto/vericto-proxy). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-only).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • 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.Unverified
Stability & Change Management0
  • 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.Unverified
Tool Coverage0
  • 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.Unverified
Tool Safety0
  • 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.Unverified
Capabilities0
  • 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

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. How we score packages →

What we tested

Checks we ran (6)

  • Known CVEs
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (8)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityNo 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.
  • Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
  • Dependency health in Supply Chain SecurityDependency 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.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)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 in Stability & Change Management (scores 0 for this)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 in Tool Coverage (scores 0 for this)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 in Tool Safety (scores 0 for this)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 in Capabilities (scores 0 for this)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.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 −6
    • CVE-2026-84243 affects this package: none ▼ security
    • Known CVEs: pass → fail ▼ security
  • 5 Nov 26 +6
    • CVE-2026-97399 no longer affects this package ▲ security
    • CVE-2026-89092 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
  • 4 Nov 26 +2
    • 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 functional
  • 1 Nov 26 20

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Analysed oci/docker.io/vericto/vericto-proxy@5.0.0@sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via OCI referrers API
Source repo vericto/vericto-proxy
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/vericto/vericto-proxy/.github/workflows/release.yml@refs/tags/v5.0.0
Rekor log index 3681011127
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:4cec9c42f94946a6e0509192b89b63bd71450a7f27088496b034c9dd76791fa9

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
CGA-vmwj-jjh8-4jc2 CVE-2026-84243 none no
CGA-vqgw-m6g6-pc47 CVE-2026-84243 none no

Background: What a vulnerability scan can and cannot prove →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

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.

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.

oci · docker.io/vericto/vericto-proxy

# add to Claude Code
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.

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.