portfolio-mcp@0.0.5
CAUTION· static onlyPublisher claims: "Portfolio analysis MCP server powered by mcp-refcache - Comprehensive portfolio metrics, optimization, and risk analysis" 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 coingecko.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-14 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. 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
# mkdir -p ~/.kubeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# echo "${{ secrets.KUBECONFIG }}" | base64 -d > ~/.kube/configFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# echo "${{ secrets.KUBECONFIG }}" | base64 -d > ~/.kube/configFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Admin tools are registered but require admin privileges (disabled by default).Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."""Check if the current context has admin privileges."""Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- `enabled` (boolean, optional): Whether to enable test context mode. Default: `true`Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.To enable admin access, override the `is_admin` function in `app/server.py` with your authentication logic.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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
Not checked against OSV yet; the weekly check has not reached this version.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim l4b4r4b4b4-lucas.cansino: 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.
- References a credential file in the home directory≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.