static-hosting-mcp@0.1.0
CAUTION· static onlyPublisher 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.
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 onlyThis 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
incomplete, 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.``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.with 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.fixture (``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.# 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.# (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.``.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.``~/.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.drops 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.``.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."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."(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.Needs 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.(``.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.of 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.still 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.Cost to the agent
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%- 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.
- 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.