meraki-magic-mcp@0.1.0
CAUTION· static onlyPublisher claims: "Meraki Magic MCP Server" 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
MAX_RESPONSE_TOKENSMERAKI_API_KEYConfiguration, not credentials: CACHE_TTL_SECONDS, ENABLE_CACHING, ENABLE_FILE_CACHING, MAX_PER_PAGE, MCP_HOST, MCP_PORT, MCP_TRANSPORT, MERAKI_ORG_ID, READ_ONLY_MODE, RESPONSE_CACHE_DIR- Where it talks to
- no vendor host named in the code
- 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-11 and scored it 66/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
COPY pyproject.toml README.md .env-example ./Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."hint": "Set READ_ONLY_MODE=false in .env to enable"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.cp .env-example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.print("FATAL: MERAKI_API_KEY is not set. Add it to .env or the environment.", file=sys.stderr)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- **Security**: Do not commit real credentials or tokens. Use placeholders and document required env vars or files. The `.env` file is used for secrets and must never be committed.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Edit .env with your MERAKI_API_KEY and MERAKI_ORG_IDFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.load_dotenv(Path(__file__).resolve().parent / ".env")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 meraki-magic-mcp@0.1.0 as of 3d ago. This is the package itself, not its dependencies.
What would make this Verified
14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim pypi: 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.