proxy-ad-research@1.3.3
CAUTION· static onlyPublisher claims: "Use for creative strategy, marketing engineering and competitor ad research on live ad-library data (Meta Ad Library/Facebook/Instagram, Google Ads Transparency Center, LinkedIn Ad Library, TikTok). Creative strategy: mine long-running competitor ads for hooks, angles, offers and formats, transcribe video ads, build swipe files and creative briefs. Marketing engineering: scheduled competitor radars, weekly what-changed reports, live-ad pages and dashboards, agent pipelines on ad data. E.g. "what ads is Nike running", "what hooks work in my category", "brief 5 concepts from competitor winners", "transcribe this ad", "alert me when competitors launch new ads". Proxy is an MCP server; no API keys, OAuth only." 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.
What changed since 1.3.2
vet-skills diff proxy-ad-research 1.3.2 1.3.3In the sandbox, this version reached for nothing 1.3.2 did not. Compared from the two recorded runs, not from source.
1.3.3 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-20 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
- Hermes Agent: add to `~/.hermes/config.yaml` under `mcp_servers:` → `proxy: {url: "https://mcp.useproxy.dev/mcp?ref=hermes", auth: oauth}`, then `hermes mcp login proxy` and `/reload-mcp`Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.No other findings across 128 lines in 2 files.
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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim tanmayjain-bit: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.