io.github.GillMacedo/slowplan
NPM · SLOWPLAN
Find why a PostgreSQL query is slow from its EXPLAIN output, without a database connection.
Available components
Last scanned (10 hours ago)
Scores higher than 48% of npm 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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 256 tokens (~128/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 72
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 5 Nov 2026 · Analysed npm/slowplan@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
postgres_plan_compare Compare two PostgreSQL query plans ~115
Compares EXPLAIN output from before and after a change, such as a new index, and shows the timing change and which problems were fixed, remain or are new. It never connects to a database.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | EXPLAIN output after the change |
| after_path | string | – | Path to a file with the plan after the change |
| before | string | – | EXPLAIN output before the change |
| before_path | string | – | Path to a file with the plan before the change |
| Name | Type | Req | Description |
|---|---|---|---|
| after_ms | number | yes | – |
| before_ms | number | yes | – |
| change_percent | number | yes | – |
| fixed | null|array | yes | – |
| new | null|array | yes | – |
| notes | null|array | yes | – |
| remaining | null|array | yes | – |
No examples provided.
postgres_plan_review Review a PostgreSQL query plan ~141
Finds why a PostgreSQL query is slow from its EXPLAIN output, in text or JSON: where the time goes, and problems such as sequential scans throwing away rows, wrong row estimates, sorts and hashes spilling to disk, and nested loops run many times. Use after running EXPLAIN (ANALYZE, BUFFERS). It only reads the text you give it and never connects to a database. Suggested indexes are candidates to test.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a file holding EXPLAIN output. Give this or plan |
| plan | string | – | EXPLAIN output as text or JSON. Give this or path |
| Name | Type | Req | Description |
|---|---|---|---|
| analyzed | boolean | yes | – |
| execution_ms | number | yes | – |
| findings | null|array | yes | – |
| hottest | null|array | yes | – |
| notes | null|array | yes | – |
| planning_ms | number | yes | – |
No examples provided.
How do I install the io.github.GillMacedo/slowplan MCP server?
io.github.GillMacedo/slowplan runs locally as an npm package, launched with npx -y slowplan. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · slowplan
claude mcp add gillmacedo-slowplan -- npx -y slowplan
What is the io.github.GillMacedo/slowplan MCP server?
io.github.GillMacedo/slowplan is an MCP server listed in the public MCP registry as io.github.GillMacedo/slowplan. Find why a PostgreSQL query is slow from its EXPLAIN output, without a database connection. This page covers its npm package (slowplan).
Is the io.github.GillMacedo/slowplan MCP server safe to use?
io.github.GillMacedo/slowplan scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.GillMacedo/slowplan MCP server expose?
io.github.GillMacedo/slowplan exposes 2 tools: postgres_plan_compare, postgres_plan_review. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.
Is the io.github.GillMacedo/slowplan MCP server still maintained?
io.github.GillMacedo/slowplan is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.GillMacedo/slowplan MCP server under?
io.github.GillMacedo/slowplan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.