PG Bloat Detective
PYPI · PG-BLOAT-DETECTIVE
Read-only Postgres bloat verdicts: blockers, timelines, REINDEX proof.
Available components
Last scanned (25 minutes ago)
Scores higher than 77% of PyPI servers
Category Databases
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to r69shabh/pg-bloat-detective). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 705 tokens (~141/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 14 Oct 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- 12 Oct 26 49
First indexed and scored.
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 17 Oct 2026 · Analysed pypi/pg-bloat-detective@0.1.6
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | r69shabh/pg-bloat-detective |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/r69shabh/pg-bloat-detective/.github/workflows/publish.yml@refs/tags/v0.1.6 |
| Rekor log index | 3230511891 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0431d503899059e69bfd3e0f2e07146b6f65455b1be4c70a2aac2c819c774af0 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bloat_blockers ~133
Who is pinning VACUUM: blocker pid + query + xmin age + slot. Read-only on the local timeline file. Priority: prepared-xact > stale-slot > idle-in-transaction. Fix: end the named session, then VACUUM the table. Args: db: Path to the SQLite timeline file (default: BLOAT_DB env). Returns: {blockers: [{ts, kind, pid, age, query, slot}] — newest first, max 20. Use pid with SELECT pg_terminate_backend(pid) after verification.
| Name | Type | Req | Description |
|---|---|---|---|
| db | string | – | – |
No output schema declared.
No examples provided.
bloat_check ~167
Diagnose PostgreSQL bloat from a collected timeline. Read-only: only reads the local SQLite timeline file, never touches Postgres. Args: db: Path to the SQLite timeline file (default: BLOAT_DB env, 'timeline.db'). Collect one first with bloat_collect, or pass any timeline.db path. Returns: findings: list of {table, verdict, evidence, action} — verdict is one of normal | vacuum-starved | blocked-by-idle-xact | blocked-by-slot | blocked-by-prepared | blocked-by-active-xact | needs-rewrite | index-bloated | index-unused. Evidence carries dead/live counts, pgstattuple approx %, pgstatindex %, blocker pid+query.
| Name | Type | Req | Description |
|---|---|---|---|
| db | string | – | – |
No output schema declared.
No examples provided.
bloat_collect ~130
Take a read-only Postgres snapshot into the timeline, then return fresh verdicts. Safe on prod: read-only transaction, 5s statement timeout, needs only pg_stat_* views + optional pgstattuple extension. No writes, no agents. Args: dsn: Postgres DSN, e.g. 'dbname=app user=readonly host=db.internal'. Default: BLOAT_DSN env. Never logs the password. Returns: {snapshot: 'saved', db: path, findings: [...with action per table/index]}.
| Name | Type | Req | Description |
|---|---|---|---|
| dsn | string | – | – |
No output schema declared.
No examples provided.
bloat_live_diagnose ~124
One-shot live diagnosis without touching your timeline file. Snapshots into a throwaway temp DB, diagnoses, discards it. Read-only on Postgres (read-only tx, 5s timeout). Safest option for prod DSNs. Args: dsn: Postgres DSN (default: BLOAT_DSN env). Password never logged. Returns: {findings: [...with action], blockers: [...]} — same verdict set as bloat_check, plus the current xmin-holder evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| dsn | string | – | – |
No output schema declared.
No examples provided.
bloat_timeline ~151
Dead-tuple + approx + index-bloat time series: when the bloat started. Read-only on the local timeline file. Args: table: Table name to filter (e.g. 'churn'). Empty = all tables. db: Path to the SQLite timeline file (default: BLOAT_DB env). Returns: {table: {dead: [{ts, live, dead}], approx_pct: [{ts, dead_pct}]}, index_bloat: {index: [{ts, bloat_pct}]}}. Rising dead = vacuum-starved; spike-then-zero = was blocked, blocker left.
| Name | Type | Req | Description |
|---|---|---|---|
| db | string | – | – |
| table | string | – | – |
No output schema declared.
No examples provided.
How do I install the PG Bloat Detective MCP server?
PG Bloat Detective runs locally as a PyPI package, launched with uvx pg-bloat-detective. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pg-bloat-detective
claude mcp add r69shabh-pg-bloat-detective -- uvx pg-bloat-detective
What is the PG Bloat Detective MCP server?
PG Bloat Detective is an MCP server listed in the public MCP registry as io.github.r69shabh/pg-bloat-detective. Read-only Postgres bloat verdicts: blockers, timelines, REINDEX proof. This page covers its PyPI package (pg-bloat-detective).
Is the PG Bloat Detective MCP server safe to use?
PG Bloat Detective scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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.
What tools does the PG Bloat Detective MCP server expose?
PG Bloat Detective exposes 5 tools: bloat_check, bloat_collect, bloat_timeline, bloat_blockers, bloat_live_diagnose. Their descriptions and schemas cost roughly 705 tokens of context every time the server is loaded.
Is the PG Bloat Detective MCP server still maintained?
PG Bloat Detective is still listed as active in the MCP registry. We last reached this channel on 17 October 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 PG Bloat Detective MCP server under?
PG Bloat Detective declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.