Skills/PyPI/rewire-genomics-mcp

rewire-genomics-mcp@0.1.0

CAUTION· not started

Publisher claims: "MCP server for bounded genomic data retrieval and versioned reference evidence" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher rewire-bio · publishing for 45 daysInstalls 58Last detonated 18 min ago

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
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso ebi.ac.uk, nih.gov, ega-archive.org, encodeproject.org, ensembl.org, genenames.org, broadinstitute.org, uniprot.org, opentargets.org, alphagenomedocs.com, githubusercontent.com, amazonaws.com, alphagenome.google — 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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- uvx rewire-genomics-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-16 and scored it 75/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: Access to sensitive file paths; Access to sensitive file paths; Reads credential paths from 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.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathssrc/genomics_mcp/storage/s3.py:106 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""A botocore session that cannot read environment variables, ~/.aws or metadata."""Fix: 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/genomics_mcp/archives/_common/http.py:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesClients built by `make_client` use `trust_env=False`: no proxy variables, no .netrc,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
CRITICAL
Reads credential paths from the home directorysrc/genomics_mcp/security.py:123 · Reads credential paths from the home directorythere, so SDKs cannot read ~/.aws or ~/.boto.Fix: 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/genomics_mcp/archives/_common/http.py:53 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""An httpx client that ignores environment proxies/.netrc and never follows redirects itself."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
CRITICAL
Reads credential paths from the home directorysrc/genomics_mcp/storage/s3.py:106 · Reads credential paths from the home directory"""A botocore session that cannot read environment variables, ~/.aws or metadata."""Fix: 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/genomics_mcp/archives/ega/access.py:17 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesvalue is registered for redaction. No `~/.aws`, keychain or default credential discovery.Fix: 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/genomics_mcp/config.py:252 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Explicit credentials for a profile, or None for anonymous. Never consults AWS_* or ~/.aws."""Fix: 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/genomics_mcp/security.py:123 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesthere, so SDKs cannot read ~/.aws or ~/.boto.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
≈59 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

5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Reads credential paths from the home directory≈ +9 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  2. Unclaimed publisher≈ +8 on the totalClaim rewire-bio: 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.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim rewire-bioPropose a patch to the maintainer