MCP servers › io.github.sumioshi › wacrew
MCP server · registry snapshot 2026-11-16 · last checked 2026-11-15
wacrew MCP server
Registry name io.github.sumioshi/wacrew
by sumioshi · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
WhatsApp for AI agents: read chats, transcribe voice notes and reply at a human pace. — the publisher's description
Summary
io.github.sumioshi/wacrew is a local MCP server listed in the official MCP registry at version 0.1.1 (marked deprecated there), under the namespace of the GitHub account sumioshi. Its linked repository, github.com/sumioshi/wacrew, belongs to the same GitHub account.
Record checks
- not met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: deprecated in the registry
- Not ranked by stars: deprecated in the registry
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- a secret: WAC_CLOUD_PASS · settings: WAC_CLOUD_URL, WAC_CLOUD_USER
- Package
- npm · listed version behind the latest release
- License
- Apache-2.0
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. So there is no tool-list size and no result from the three APIs.
Worth knowing before you connect it
- The registry marks this server deprecated.
- The registry lists 0.1.1; 0.1.2 is newer (1 release).
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.1.1, published 2026-11-14 (registry, as of the 2026-11-16 snapshot)
- First listed version
- 2026-11-14 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, all on 2026-11-14; 2 in the 90 days before the 2026-11-16 snapshot; 2 marked deprecated.(versions still listed in the registry only)
Most recent 2 versions
0.1.1· 2026-11-14 · deprecated0.1.0· 2026-11-14 · deprecated
- Registry data
- snapshot 2026-11-16
- Package and repository
- checked 2026-11-15
Dead or stale signals
1 found in the records we hold
- The registry marks this entry deprecated. — MCP registry · 2026-11-16 · all servers with this fact
Looked for and not found: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.1.0 (published 2026-11-14) → 0.1.1 (published 2026-11-14), between the registry lists of 2026-11-14 and 2026-11-15.
The publisher published no GitHub release note for version 0.1.1: the repository has no release tagged for it and named for this package (the repository holds several packages).
Source: the official MCP Registry list on 2026-11-14 and on 2026-11-15; release notes from the GitHub Releases API, checked 2026-11-15.
What it is
How do I add it to my client?
Config from the registry entry
From the npm package wacrew-mcp
This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"wacrew": {
"command": "npx",
"args": [
"-y",
"wacrew-mcp@0.1.1"
],
"env": {
"WAC_CLOUD_URL": "<WAC_CLOUD_URL>",
"WAC_CLOUD_USER": "<WAC_CLOUD_USER>",
"WAC_CLOUD_PASS": "<WAC_CLOUD_PASS>"
}
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"wacrew": {
"command": "npx",
"args": [
"-y",
"wacrew-mcp@0.1.1"
],
"env": {
"WAC_CLOUD_URL": "<WAC_CLOUD_URL>",
"WAC_CLOUD_USER": "<WAC_CLOUD_USER>",
"WAC_CLOUD_PASS": "<WAC_CLOUD_PASS>"
}
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"wacrew": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"wacrew-mcp@0.1.1"
],
"env": {
"WAC_CLOUD_URL": "${input:wac-cloud-url}",
"WAC_CLOUD_USER": "${input:wac-cloud-user}",
"WAC_CLOUD_PASS": "${input:wac-cloud-pass}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "wac-cloud-url",
"description": "WAC_CLOUD_URL",
"password": true
},
{
"type": "promptString",
"id": "wac-cloud-user",
"description": "WAC_CLOUD_USER",
"password": true
},
{
"type": "promptString",
"id": "wac-cloud-pass",
"description": "WAC_CLOUD_PASS",
"password": true
}
]
}Claude Code
claude mcp add --env "WAC_CLOUD_URL=<WAC_CLOUD_URL>" "WAC_CLOUD_USER=<WAC_CLOUD_USER>" "WAC_CLOUD_PASS=<WAC_CLOUD_PASS>" --transport stdio wacrew -- npx -y wacrew-mcp@0.1.1
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"wacrew": {
"command": "npx",
"args": [
"-y",
"wacrew-mcp@0.1.1"
],
"env": {
"WAC_CLOUD_URL": "<WAC_CLOUD_URL>",
"WAC_CLOUD_USER": "<WAC_CLOUD_USER>",
"WAC_CLOUD_PASS": "<WAC_CLOUD_PASS>"
},
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"wacrew": {
"command": "npx",
"args": [
"-y",
"wacrew-mcp@0.1.1"
],
"env": {
"WAC_CLOUD_URL": "<WAC_CLOUD_URL>",
"WAC_CLOUD_USER": "<WAC_CLOUD_USER>",
"WAC_CLOUD_PASS": "<WAC_CLOUD_PASS>"
}
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.wacrew] command = "npx" args = ["-y", "wacrew-mcp@0.1.1"] [mcp_servers.wacrew.env] "WAC_CLOUD_URL" = "<WAC_CLOUD_URL>" "WAC_CLOUD_USER" = "<WAC_CLOUD_USER>" "WAC_CLOUD_PASS" = "<WAC_CLOUD_PASS>"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"wacrew": {
"command": "npx",
"args": [
"-y",
"wacrew-mcp@0.1.1"
],
"env": {
"WAC_CLOUD_URL": "<WAC_CLOUD_URL>",
"WAC_CLOUD_USER": "<WAC_CLOUD_USER>",
"WAC_CLOUD_PASS": "<WAC_CLOUD_PASS>"
}
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -e "WAC_CLOUD_URL=<WAC_CLOUD_URL>" -e "WAC_CLOUD_USER=<WAC_CLOUD_USER>" -e "WAC_CLOUD_PASS=<WAC_CLOUD_PASS>" -- npx -y wacrew-mcp@0.1.1
- Replace <WAC_CLOUD_URL>, <WAC_CLOUD_USER>, <WAC_CLOUD_PASS> with your own values; the entry marks WAC_CLOUD_PASS as secret, so keep the file out of version control.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.1.1
- Latest stable
- 0.1.2
- Status
- behind the latest release (1 releases, 0 days)
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-15. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-15 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-Oh2iW4ffReBycfeI0…
- Signature
- signed
- License
- Apache-2.0
Source: the package registry · 2026-11-15.
Usage
- Downloads
- 748 in the last month
Source: api.npmjs.org · 2026-11-15.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 0.1.1). Source: registry.npmjs.org/wacrew-mcp/0.1.1 · read 2026-11-15.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/wacrew-mcp/0.1.1 · read 2026-11-15.
- Node.js version (npm). Needs Node 20 or later (engines.node
>=20). Source: registry.npmjs.org/wacrew-mcp/0.1.1 · read 2026-11-15. - MCP SDK in the package files. The package ships MCP SDK code inside its own files (1 file) but does not list
@modelcontextprotocol/sdkor any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency, so its SDK version is fixed at build time. Bundled SDK version: not read. Source: registry.npmjs.org/wacrew-mcp/-/wacrew-mcp-0.1.1.tgz · read 2026-11-15. - Build workflow. No build provenance published for this version. Source: registry.npmjs.org/wacrew-mcp/0.1.1 · read 2026-11-15.
Registry entry
- Same package in other registry entries. The same npm package
wacrew-mcpis also listed by another registry entry,io.github.sumioshi/wacrew-whatsapp-mcp, at a newer version (0.1.4; this entry lists 0.1.1). Source: own registry snapshot · read 2026-11-18.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-18. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Own host
- security.txt. No security.txt at https://wacrew.com.br/.well-known/ (HTTP 404, 2026-11-15). Source: wacrew.com.br/.well-known/security.txt · read 2026-11-15.
- A2A agent card. No A2A agent card at https://wacrew.com.br/.well-known/ (HTTP 404, 2026-11-15). Source: wacrew.com.br/.well-known/agent-card.json · read 2026-11-15.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.1.1 on npm | Exists and can be installed | matches | npm · 2026-11-15 |
| Repository github.com/sumioshi/wacrew | Opens publicly | matches | api.github.com · 2026-11-15 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.sumioshi · 2 servers
- GitHub owner
- a personal account (sumioshi)
- Build record
- signed
- Repository
- github.com/sumioshi/wacrew
- Stars
- 4
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-15; security policy read from GitHub · 2026-11-14.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- Not ranked by downloads: deprecated in the registry
- Not ranked by stars: deprecated in the registry
- Not metRegistry entry is active and says how to run itThe registry marks this entry as deprecated.What changes this check: This check reads the registry entry's status and whether it lists a package or a remote address. Marking an entry deprecated is the publisher's own choice. The registry's documentation says a published version's metadata cannot be changed; a new server.json with a unique version string is how an entry is updated. Versioning published MCP servers
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierApache-2.0
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-15 (security policy 2026-11-14). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.sumioshi/wacrew
Answered from the data aboveWho publishes io.github.sumioshi/wacrew?
The registry ties the namespace io.github.sumioshi to the GitHub account sumioshi; only its owner can publish under it. Its linked repository, github.com/sumioshi/wacrew, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.sumioshi/wacrew safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. Its registry entry is marked deprecated. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.sumioshi/wacrew been security tested?
No. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Does io.github.sumioshi/wacrew publish a security policy?
Yes: its repository has a public security policy (github.com/sumioshi/wacrew/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
No. The registry lists 0.1.1; the latest stable release on npm is 0.1.2.
Where is the source code of io.github.sumioshi/wacrew?
In github.com/sumioshi/wacrew, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. — the server's own choice
Required inputs the publisher declares: WAC_CLOUD_URL, WAC_CLOUD_USER, WAC_CLOUD_PASS (secret).
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.sumioshi/wacrew: MCP server record.” Data checked 2026-11-15. https://protocolprobe.com/mcp/servers/io.github.sumioshi/wacrew
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.sumioshi/wacrew)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology