SQLite Npx vs Postgres · modelcontextprotocol
SQLite Npx scores 20 points higher on the same evidence, which is a real separation rather than noise. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| SQLite Npx | Postgres · modelcontextprotocol | what it means | |
|---|---|---|---|
| tashan score | 38 | 18 | upkeep + freshness, gated by adoption |
| Adoption evidence | 3k/wk | 127k/wk | the raw public signal the score came from |
| Last release | abandoned | abandoned | npm publish or repo push |
| Upkeep | 44 | 18 | cadence, maintainers, status |
| Expertise grade | not graded | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories, no build provenance | existence of findings is always free; the detail a licence buys is on each dossier |
| Licence | ISC | MIT | |
| Maintainers | one primary | more than one | bus-factor risk |
Install either
SQLite Npx
claude mcp add mcp-server-sqlite-npx -- npx -y mcp-server-sqlite-npxPostgres · modelcontextprotocol
claude mcp add modelcontextprotocol-server-postgres -- npx -y @modelcontextprotocol/server-postgresNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each, including what a licence adds, is on its own page: SQLite Npx · Postgres · modelcontextprotocol.