Unreleased: not public yet. Maintainers have not reviewed this result.
Results / mcp-sqlite
mcp-sqlite
A
Protocol4/4 points
F
SQLite1/7 pointscritical: sqlite-mutating-sql, sqlite-file-read, sqlite-file-write
Coverage: low (1 of 8 tools reached with a valid call).
Protocol checks
| Check | Verdict | What happened |
|---|---|---|
| protocol Valid MCP handshake and tool schemas | pass | handshake ok, 8 well-formed tool(s) |
| tool-poisoningcritical No tool-poisoning indicators in tool metadata | pass | scanned 8 tool definition(s), including parameter text: nothing suspicious |
| robust-input Survives malformed tool input | pass | 24 invalid call(s) rejected cleanly |
| secret-echocritical No environment secret echoed in responses | pass | canary secrets absent from tools/list and 24 captured response(s) |
SQLite checks
| Check | Verdict | What happened |
|---|---|---|
| sqlite-read-only SQLite: read-only by default | fail | writes executed on every SQL tool (query) |
| sqlite-mutating-sqlcritical SQLite: mutating SQL blocked | fail | EXECUTED: comment-obfuscation, cte-insert, replace-into, upsert, create-table, alter-table, drop-table, pragma-user-version, pragma-journal-mode; 1 of 10 blocked |
| sqlite-file-readcritical SQLite: no reading of other files | fail | a database outside the fixture was attached and read through every tool |
| sqlite-file-writecritical SQLite: no writing of other files | fail | files were written to the canary directory through every tool |
| sqlite-extension-loadcritical SQLite: no loading of extensions | pass | extension loading was refused on 1 tool(s) |
| sqlite-rowcap SQLite: row cap | fail | no row cap was in effect (see the evidence for what came back) |
| sqlite-timeout SQLite: query timeout | fail | a runaway query was not cancelled |
What was not covered
- Database: Not applicable. Server config has no {dsn}/{host}/... Placeholder, so the harness cannot start the server once per role
- HTTP: Not applicable. The server is started over stdio; the http pack needs server.url
- Files: Not applicable. No tool is classified as taking a file path with medium confidence or higher
- Git: Not applicable. No tool is classified as taking a git repository path with medium confidence or higher
- Network: Not applicable. No tool is classified as taking a URL with medium confidence or higher
- Effects: Not applicable. No tool takes a harness-owned target (file path, repository or URL) with medium confidence or higher
- Tool "(engine)" was not covered by the sqlite pack: engine has no roles or grants; row filtering and masking are not graded
- Tools that a server lists only for clients that declare roots, sampling or elicitation capabilities are not seen: the harness declares none
- Tool "db_info" is covered by the core checks only: the tool takes no parameters; add it under tools: to include it
- Tool "list_tables" is covered by the core checks only: the tool takes no parameters; add it under tools: to include it
- Tool "get_table_schema" is covered by the core checks only: string parameters only, and none names a path, URL, command, SQL or repository; add it under tools: to include it
- Tool "create_record" is covered by the core checks only: string parameters only, and none names a path, URL, command, SQL or repository; its required parameter "data" cannot be filled by the harness; write a probes: entry to call it
- Tool "read_records" is covered by the core checks only: string parameters only, and none names a path, URL, command, SQL or repository; add it under tools: to include it
- Tool "update_records" is covered by the core checks only: string parameters only, and none names a path, URL, command, SQL or repository; its required parameters "data", "conditions" cannot be filled by the harness; write a probes: entry to call it
Run it yourself
Started with the standard settings like this; put it in sealmark.yaml as the server:
npx -y mcp-sqlite@1.0.9
Each of 613 verdicts was checked independently, and Sealmark was wrong on some: how reliable Sealmark is.
Think a verdict is wrong, or want a server removed? Email disclosure@sealmark.dev with the server version. We recheck, correct the page if we were wrong, and add your reply. See the disclosure policy.