Chroma’s official MCP server: vector search and collection management for RAG workflows.
Vericto Proxy mode (local, PostgreSQL) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read-only PostgreSQL for AI agents: every statement is checked before it runs. No account needed.
Quickstart
Install it the way its author documents:
The full guide: https://github.com/vericto/vericto-proxy
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Vericto Proxy mode (local, PostgreSQL) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Install it the way its author documents:
The full guide: https://github.com/vericto/vericto-proxy
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
The workspace's rules in force on this database (from the signed bundle this server syncs): code, severity, type and the action they resolve to. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| active_only | boolean | no | — |
One rule's detail by code (e.g. VERICTO-001): severity, the action it resolves to, its type and, for a custom rule, its condition. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | Rule code, e.g. VERICTO-001 (case-insensitive) |
Evaluate SQL against this workspace's rules without running it: findings with their line, BLOCKED / FLAGGED / MONITORED, suggested fixes and the masked rewrite a policy would run. Evaluated locally by the same evaluator execute_sql uses (no CI checks are spent). Pass a whole…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sql | string | no | A whole SQL script, split into statements. Use this OR queries. |
| queries | array | no | Pre-split statements. Use this OR sql. |
| dialect | string | no | postgres (this server's database is PostgreSQL). |
| file_name | string | no | — |
| database_id | string | no | Ignored: this server serves one database. |
| verbose | boolean | no | Also return every statement's verdict. |
| ticket | string | no | — |
This server's database (name, dialect), the permission tiers enabled (read only), the result limits, the ruleset version (an earlier verdict holds while it is unchanged), whether a Vericto control plane is linked or the server runs locally on the built-in ruleset, the identity calls are recorded…
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Vericto Proxy mode (local, PostgreSQL) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 4.23.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Vericto Proxy mode (local, PostgreSQL) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.