Chroma’s official MCP server: vector search and collection management for RAG workflows.
Nothing to run from here
PostgreSQL Performance (read-only) 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.
—
trust score
—
calls last 7d
local
runs on your machine
—
p95 latency
What it does
Read-only PostgreSQL performance diagnosis for AI assistants. It finds the slowest queries in pg_stat_statements, summarizes EXPLAIN plans, suggests indexes and checks them with hypothetical indexes (hypopg), reports table health and lock contention, and shows the plans of the queries running inside database functions.
Read-only by design: every query is checked against a single-SELECT allowlist and runs in a read-only transaction that is always rolled back, under a read-only role, with timeouts and a row cap. Index suggestions are returned as text and never executed.
Quickstart (Docker):docker run --rm -p 127.0.0.1:8080:8080 -e PGPERF_DB_URL=jdbc:postgresql://host.docker.internal:5432/mydb -e PGPERF_DB_USER=mcp_readonly -e PGPERF_DB_PASSWORD=<role password> -e MCP_API_KEY=<32+ random characters> ghcr.io/gouranshul/pg-perf-mcp:0.1.0
Then connect your client to http://localhost:8080/mcp (Streamable HTTP) with the header Authorization: Bearer <MCP_API_KEY>.
Claude Code: claude mcp add --transport http pg-perf http://localhost:8080/mcp --header "Authorization: Bearer <MCP_API_KEY>"or install the plugin: /plugin install pg-perf --marketplace gouranshul/pg-perf-mcp
Database setup (read-only role, pg_stat_statements) and Cursor / VS Code configs: https://github.com/gouranshul/pg-perf-mcp#quickstartReport a vulnerability: https://github.com/gouranshul/pg-perf-mcp/security
Quickstart
This image runs as a local HTTP server (Streamable HTTP), not over stdio, and the port it listens on is not recorded here, so there is no line to print: start it the way its own source says, publishing that port with -p, then add its address to your client as a remote server.
Publisher
Installation
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 PostgreSQL Performance (read-only) 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.
This image runs as a local HTTP server (Streamable HTTP), not over stdio, and the port it listens on is not recorded here, so there is no line to print: start it the way its own source says, publishing that port with -p, then add its address to your client as a remote server.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No tool surface on file
This listing has not published its tool list here yet. Nothing is shown here rather than another listing’s tools, which is what this page used to do.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- 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 PostgreSQL Performance (read-only) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish PostgreSQL Performance (read-only) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.