ntfy-blade-mcp@0.2.0
CAUTION· static onlyPublisher claims: "ntfy push notification MCP Server — publish, poll, topic and token management" 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
NTFY_MCP_API_TOKENNTFY_TOKENConfiguration, not credentials: NTFY_BASE_URL, NTFY_DEFAULT_TOPIC, NTFY_MCP_PORT, NTFY_WRITE_ENABLED, TRANSPORT- Where it talks to
- no vendor host named in the codeAlso ntfy.sh — 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-13 and scored it 72/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
No findings across 2,106 lines in 20 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
No advisories in OSV for ntfy-blade-mcp@0.2.0 as of 27 h ago. This is the package itself, not its dependencies.
What would make this Verified
8 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim piers: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.