whatsapp-mcp@0.0.1
CAUTION· install onlyPublisher claims: "Enables MCP clients such as ChatGPT, Claude, or Grok to search and read a user's own WhatsApp message history through a linked device, without sending, editing, or deleting messages." Observed in sandbox: reads credential files.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 4 of 4 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
CLOUDFLARE_API_TOKENOAUTH_KVOAUTH_PROVIDERWA_OWNER_PASSWORDConfiguration, not credentials: ALERT_EMAIL, ALERT_FROM, ALERT_TO, CLOUDFLARE_ACCOUNT_ID, CONTACT_X, DEFAULT_COUNTRY_CODE, LOGIN_URL, MAX_DB_MB, MAX_MESSAGES, OPEN_SIGNUP, OPERATOR_NAME, REGISTRY, SIGNUP_LIMIT, TIMEZONE, TRANSCRIBE_MODEL, WA_PIN- Where it talks to
- whatsapp.net, whatsapp.com (its own)Also x.com, cloudflare.com, finereli.com, claude.ai, chatgpt.com, grok.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- read ~/.npmrc · reached only registry.npmjs.org
- What we could not test
- use of the skill by an agent
Connect it only under the guard, with no real credential files on the machine it runs on. It read ~/.npmrc, which is nothing an MCP server needs from a user. `--contain` makes those directories unreadable.
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 ran it in the KillerSkills honeypot sandbox (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-21 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. Notable findings: Access to sensitive file paths. Summary: reads credential files.
Behavior trace
Honeypot run · 16 s · 3 scenariosStatic findings
env_file: .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.4. Done means all three are green: `npm test`, `npm run typecheck`, and `npx wrangler deploy --dry-run --outdir /tmp/dryrun` (proves the bundle builds).Fix: Pin versions and sources; vendor anything fetched at install time.&& rm -rf /var/lib/apt/lists/* \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.PUBLIC_HOST: ${PUBLIC_HOST:?set PUBLIC_HOST in .env}Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "Neither WA_OWNER_PASSWORD nor OPEN_SIGNUP=true is set in .env, so nobody can sign in." >&2Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.initSchema(this.host.ctx.storage.sql); // puts the trigger backFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const sentAsLid = written(this.sql.exec(`DELETE FROM lid_senders WHERE sender = ?`, L)) > 0;Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.exec npx wrangler dev --ip 0.0.0.0 --port 8787 --persist-to /data \Fix: Pin versions and sources; vendor anything fetched at install time.this.sql.exec(`UPDATE messages SET sender = ?, data = ? WHERE chat = ? AND id = ?`, P, this.vault.seal(blob, MSG), r.chat, r.id);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const existing = this.sql.exec<{ sender: string | null; data: ArrayBuffer }>(`SELECT sender, data FROM messages WHERE chat = ? AND id = ?`, cid, ev.id).toArray()[0];Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.this.sql.exec(`UPDATE messages SET sender = COALESCE(sender, ?), data = ? WHERE chat = ? AND id = ?`, sender, this.vault.seal(blob, MSG), cid, ev.id);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(`Check it with: npx wrangler deploy -c ${out} --dry-run`);Fix: Pin versions and sources; vendor anything fetched at install time.if (sentAsLid) for (const r of this.sql.exec<{ chat: string; id: string; data: ArrayBuffer }>(`SELECT chat, id, data FROM messages WHERE sender = ?`, L).toArray()) {Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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
8 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Reads credential files≈ +27 on the totalThe sandbox saw reads under ~/.ssh, ~/.aws, ~/.npmrc, ~/.config or similar. Read only files inside the project, and only the ones the task needs. Seen: ~/.npmrc.
- Unclaimed publisher≈ +8 on the totalClaim engdawood: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- 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.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.