registry / record

github.com/motherduckdb/mcp-server-motherduck

github / sealed 2026-06-16 / No. 04abf171

Does github.com/motherduckdb/mcp-server-motherduck MCP work in Claude Code and Cursor? Throne executed github.com/motherduckdb/mcp-server-motherduck mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: needs launch arguments. Is github.com/motherduckdb/mcp-server-motherduck mcp safe? Static security scan: 4 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.

re-scan this server gate it in your CI

> throne registry github.com/motherduckdb/mcp-server-motherduck sealed

This server needs launch argumentsthe server requires command-line arguments (for example a database URL) that a bare launch does not pass, Usage: mcp-server-motherduck [OPTIONS] Try 'mcp-server-motherduck --help' for help. Error: In-memory databases require the --read-write flag. Options: - Add --read-write to allow writes (data won't persist anyway) - Use --db-path with a file path for read-only access to a DuckDB file - Use --db-path md: with a MotherDuck token for cloud database access

receiptsealed evidence

scan id: 04abf17143ba43deab553b7740f6fa90
target: https://github.com/motherduckdb/mcp-server-motherduck
sealed at: 2026-06-16 16:58:02Z
evidence hash: sha256:4a63e87e3d65c16d9720c6b9a84ecd2e732a7c1f9492f85b5e28c1aab66c0485

01connectFAIL0ms

server never launched: server process exited with code 2 before the MCP handshake, stderr: Usage: mcp-server-motherduck [OPTIONS] Try 'mcp-server-motherduck --help' for help. Error: In-memory databases require the --read-write flag. Options: - Add --read-write to allow writes (data won't persist anyway) - Use --db-path with a file path for read-only access to a DuckDB file - Use --db-path md: with a MotherDuck token for cloud database access

02discoverSKIPPED0ms

not run, server never launched

03validate_schemasSKIPPED0ms

not run, server never launched

04smoke_test_toolsSKIPPED0ms

not run, server never launched

05error_handlingSKIPPED0ms

not run, server never launched

06streamingSKIPPED0ms

not run, server never launched

07resource_lifecycleSKIPPED0ms

not run, server never launched

08concurrent_callsSKIPPED0ms

not run, server never launched

09reconnectSKIPPED0ms

not run, server never launched

01connectFAIL0ms

server never launched: server process exited with code 2 before the MCP handshake, stderr: Usage: mcp-server-motherduck [OPTIONS] Try 'mcp-server-motherduck --help' for help. Error: In-memory databases require the --read-write flag. Options: - Add --read-write to allow writes (data won't persist anyway) - Use --db-path with a file path for read-only access to a DuckDB file - Use --db-path md: with a MotherDuck token for cloud database access

02discoverSKIPPED0ms

not run, server never launched

03validate_schemasSKIPPED0ms

not run, server never launched

04smoke_test_toolsSKIPPED0ms

not run, server never launched

05error_handlingSKIPPED0ms

not run, server never launched

06streamingSKIPPED0ms

not run, server never launched

07resource_lifecycleSKIPPED0ms

not run, server never launched

08concurrent_callsSKIPPED0ms

not run, server never launched

09reconnectSKIPPED0ms

not run, server never launched

chatgpt desktop calibratingemulation profile pending real-traffic captureCOMING SOON

SECURITY: REVIEW / 4 finding(s) (2 medium) / review recommended

MEDIUMTHR-EXEC-04 / Arbitrary command execution from tool arguments

subprocess.Popen() called with a dynamically built command (heuristic, review): ''

mcp-server-motherduck-HEAD/tests/e2e/test_http_transport.py:82

MEDIUMTHR-EXEC-04 / Arbitrary command execution from tool arguments

subprocess.Popen() called with a dynamically built command (heuristic, review): ''

mcp-server-motherduck-HEAD/tests/e2e/test_http_transport.py:557

LOWTHR-NET-05 / Hardcoded outbound endpoints

1 non-local endpoint host(s) referenced in code, verify each is expected for this server's purpose: motherduck.com (mcp-server-motherduck-HEAD/src/mcp_server_motherduck/database.py:229)

mcp-server-motherduck-HEAD/src/mcp_server_motherduck/database.py:229

LOWTHR-VER-11 / Outdated MCP SDK or protocol version pin

obsolete protocol version string '2024-11-05' in source

mcp-server-motherduck-HEAD/tests/e2e/test_http_transport.py:122

VERDICT: NEEDS LAUNCH ARGUMENTSSANDBOXED RUN, submitted server executed in a disposable microVM, compatibility not assessable: needs arguments: the server requires command-line arguments (for example a database URL) that a bare launch does not pass, Usage: mcp-server-motherduck [OPTIONS] Try 'mcp-server-motherduck --help' for help. Error: In-memory databases require the --read-write flag. Options: - Add --read-write to allow writes (data won't persist anyway) - Use --db-path with a file path for read-only access to a DuckDB file - Use --db-path md: with a MotherDuck token for cloud database access / security: review, 4 finding(s), 0 highsealed by THRONE / No. 04abf171 / 2026-06-16

scopeattestation tuple

target: https://github.com/motherduckdb/mcp-server-motherduck github
engine: sandboxed
claude code: calibration: partial recorded=9,spec=0,assumed=9
cursor: calibration: partial recorded=11,spec=0,assumed=7
chatgpt desktop: calibration: unavailable recorded=0,spec=2,assumed=16
steps exercised: 18 of 18
test suite: v1.0.0
security ruleset: v1.0.0
sealed at: 2026-06-16 16:58:02Z
evidence hash: sha256:4a63e87e3d65c16d9720c6b9a84ecd2e732a7c1f9492f85b5e28c1aab66c0485
valid until: 2026-09-14

executed in a disposable microVM, created for this scan and destroyed after it. nothing outlives a run.

maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.

this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.