dryrun MCP server
PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials.
A94/100grade A
Adoption
Established
35 stars1.2k downloads/wk
Reviews
Write oneNobody has reviewed dryrun yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
dryrun tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y @boringsql/dryrun on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add dryrun -- npx -y @boringsql/dryrun
dryrun: common questions
- Is dryrun MCP server safe?
- Yes, by our scan: it is graded A (94/100). Read the dryrun safety report
- How do I install dryrun?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does dryrun need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is dryrun maintained?
- The last commit was 3 days ago (2026-09-17). The latest release is v0.17.0.