Skills/PyPI/static-hosting-mcp

static-hosting-mcp@0.1.0

CAUTION· static only

Publisher claims: "MCP server that publishes self-contained artifacts to a Google Cloud Storage bucket and manages per-object read access by Google-account email." Observed in sandbox: static analysis only — behavior not yet observed.

Registry PyPI (MCP server)Publisher bobbyhyam · publishing for 140 daysInstalls 38Last detonated 7 h ago

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

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 google.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
nothing has run yet
What we could not test
everything: the server has not run yet

Run it before you trust it. Nothing has run yet: the code was read, the server was not. `vet-skills try` runs this exact version in the honeypot in about a minute.

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 analysed it statically (a sandbox run is pending) on 2026-11-18 and scored it 63/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; Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
Access to sensitive file pathstests/conftest.py:14 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesincomplete, so ``pytest -m live`` is a clean no-op without a ``.env``.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_server_stdio.py:16 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files``test_live_integration.py`` and is gated/skipped without ``.env`` (R18, ASM8).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_live_integration.py:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswith just ``.env`` filled in, and exercises the live ACL layer when the operatorFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_live_integration.py:6 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfixture (``conftest.py``) then **skips** cleanly when the operator's ``.env`` isFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:31 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load .env once at collection time so the live tier sees the operator's config.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 pathspyproject.toml:115 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# (which need a real GCS bucket + the env vars in .env.example) are taggedFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:16 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files``.env`` is loaded at import so the live tier picks up ``GCS_BUCKET`` /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/static_hosting_mcp/server.py:485 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files``~/.config/gcloud`` / ``~/.gnupg``, any path with a ``secrets`` directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_server_stdio.py:62 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdrops the host's ``.env`` source-path knobs, so the subprocess is independentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:119 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files``.env`` is a no-op rather than a red build.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 pathspyproject.toml:120 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"live: requires a live GCS bucket and credentials (see .env.example)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:124 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"(copy .env.example to .env and fill it in); skipping."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_live_integration.py:157 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesNeeds no grantee, so it runs against any bucket with ``.env`` filled in.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_live_integration.py:107 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files(``.env`` already loaded by ``conftest.py``) so its lifespan builds the realFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_server_stdio.py:63 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesof whatever ``.env`` the operator has. ``cwd``/``PYTHONPATH`` at the repo rootFix: 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/static_hosting_mcp/server.py:484 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesstill refused): the configured service-account key, anything under ``~/.ssh`` /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
≈75 tok
1 file · 23 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for static-hosting-mcp@0.1.0 as of 6 h ago. This is the package itself, not its dependencies.

What would make this Verified

17 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim bobbyhyam: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +2 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 bobbyhyamPropose a patch to the maintainer