Skills/PyPI/duckdb-mcp-server

duckdb-mcp-server@0.1.0

CAUTION

Publisher claims: "A MCP server for DuckDB that enables LLMs to query and analyze data from various sources" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher yourusername · joined 8 days agoInstalls 106Last detonated 4d ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-10-30 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: AWS access key pattern detected; AWS access key pattern detected; References a credential file in the home directory. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1
0.1sprocessexec /usr/bin/timeout
0.1sprocessexec .venv/bin/duckdb-mcp-server
0.1sprocessexited 127: timeout: failed to run command '.venv/bin/duckdb-mcp-server': No such file or directory
0.1sclaimedno tools/list reply (exit 127)
0.1sprocessscript backend runs setup only

Static findings

HIGH
AWS access key pattern detectedsrc/duckdb_mcp_server/resources/xml/duckdb_data_import.xml:48 · AWS access key pattern detected — possible hardcoded or harvested keyFix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
File type combined with upload actionsrc/duckdb_mcp_server/resources/xml/duckdb_data_import.xml:1848 · File type combined with upload action — agent may exfiltrate local data filesFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
HIGH
AWS access key pattern detectedsrc/duckdb_mcp_server/resources/xml/duckdb_data_import.xml:209 · AWS access key pattern detected — possible hardcoded or harvested keyFix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
HIGH
References a credential file in the home directorysrc/duckdb_mcp_server/credentials.py:53 · References a credential file in the home directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
HIGH
Access to sensitive file pathssrc/duckdb_mcp_server/credentials.py:53 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/duckdb_mcp_server/database.py:15 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

What would make this Verified

10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim yourusername: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
  3. AWS access key pattern detected≈ +4 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
  4. References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  5. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  6. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim yourusername