Compared · sqlite
8 SQLite MCP servers. Which one to use.
Every SQLite server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 8 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| io.github.arifulislamat/database-mcp-sqlite | io.github.arifulislamat | no flag | REVIEW | 80 | npm @database-mcp/sqlite |
| io.github.ofershap/sqlite | io.github.ofershap | no flag | REVIEW | 76 | npm mcp-sqlite-server |
| io.github.rosch100/mcp-encrypted-sqlite | io.github.rosch100 | no flag | REVIEW | 68 | docker ghcr.io/rosch100/mcp-encrypted-sqlite:0.4.1 |
| io.github.neverinfamous/sqlite-mcp-server | io.github.neverinfamous | no flag | REVIEW | 65 | pypi sqlite-mcp-server-enhanced |
| ai.smithery/afgong-sqlite-mcp-server | ai.smithery | no flag | REVIEW | 64 | remote endpoint |
| ai.smithery/wgong-sqlite-mcp-server | ai.smithery | no flag | REVIEW | 64 | remote endpoint |
| io.github.rosch100/mcp-sqlite | io.github.rosch100 | no flag | REVIEW | 62 | docker ghcr.io/rosch100/mcp-sqlite:0.2.4 |
| io.github.spences10/mcp-sqlite-tools | io.github.spences10 | no flag | REVIEW | 52 | npm mcp-sqlite-tools |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.