Skills/PyPI/quilt-mcp

quilt-mcp@0.22.0

CAUTION· not started

Publisher claims: "Secure MCP server for accessing Quilt data with IAM or JWT authentication" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher quiltdata · publishing for 246 daysInstalls 87Last detonated 14 min ago
What would fix thisWatchDispute verdict

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
MCP_TELEMETRY_API_KEY or --jwt-tokenConfiguration, not credentials: AWS_DEFAULT_REGION, AWS_REGION, FASTMCP_ADDR, FASTMCP_HOST, FASTMCP_PORT, FASTMCP_TRANSPORT, MCP_SKIP_BANNER, MCP_TELEMETRY_BATCH_SIZE, MCP_TELEMETRY_ENDPOINT, MCP_TELEMETRY_FLUSH_INTERVAL, MCP_TELEMETRY_LEVEL, MCP_TELEMETRY_LOCAL_ONLY, MCP_TELEMETRY_PRIVACY_LEVEL, MCP_TELEMETRY_SESSION_TIMEOUT, QUILT_ALLOW_TEST_JWT, QUILT_CATALOG_URL, QUILT_DEPLOYMENT, QUILT_DISABLE_USAGE_METRICS, QUILT_MCP_RESOURCE_ACCESS_LOGGING, QUILT_MCP_RESOURCE_CACHE_ENABLED, QUILT_MCP_RESOURCE_CACHE_TTL, QUILT_MCP_RESOURCES_ENABLED, QUILT_MULTIUSER_MODE, QUILT_NAVIGATOR_URL, QUILT_REGISTRY_URL, QUILT_SERVICE_TIMEOUT, QUILT_TEST_BUCKET, QUILT_TEST_ENTRY, QUILT_TEST_PACKAGE, QUILT_WORKFLOW_DIR, TEST_QUILT_CATALOG_URL, VAR, VAR_NAME
Where it talks to
quiltdata.com, quilttest.com, quiltdata.cloud, quilt.bio (its own)Also astral.sh — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names astral.sh as well as its own vendor. The guard injects MCP_TELEMETRY_API_KEY only into requests to quiltdata.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets MCP_TELEMETRY_API_KEY=quiltdata.com -- uvx quilt-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 78/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: Pipe-to-shell pattern; Access to sensitive file paths; Access to sensitive file paths. 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.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

CRITICAL
Pipe-to-shell patternsrc/quilt_mcp/main.py:46 · Pipe-to-shell pattern — downloads and immediately executes remote codeprint(" curl -LsSf https://astral.sh/uv/install.sh | sh", file=sys.stderr)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST06
MEDIUM
Remote installer piped to shellsrc/quilt_mcp/main.py:46 · Remote installer piped to shellprint(" curl -LsSf https://astral.sh/uv/install.sh | sh", file=sys.stderr)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST07
HIGH
Access to sensitive file pathssrc/quilt_mcp/main.py:115 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesload_dotenv() # Loads from .env in current working directoryFix: 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/quilt_mcp/main.py:112 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load .env for development (project root only, not user's home directory)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈54 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.

What would make this Verified

2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Pipe-to-shell pattern≈ +9 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
  2. Unclaimed publisher≈ +8 on the totalClaim quiltdata: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. 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.
  4. Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim quiltdataPropose a patch to the maintainer