registry / record

github.com/motherduckdb/mcp-server-motherduck

github / sealed 2026-06-12 / No. 528a9649

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 — duck --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: 528a964948de4eb6859e454a5de12626
target: https://github.com/motherduckdb/mcp-server-motherduck
sealed at: 2026-06-12 06:55:08Z
evidence hash: sha256:c7debc5881ef34863259b4035005ce42bcf4b3fda633edb9e581d8764ec698ce

01connectFAIL0ms

server never launched: server process exited with code 2 before the MCP handshake — stderr: duck --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: duck --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 desktopemulation profile pending real-traffic captureCOMING SOON

SECURITY: REVIEW / 4 finding(s) / review material, not a verdict

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 — duck --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. 528a9649 / 2026-06-12

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.