Removed from the official registry (not found on 2026-10-24)

This server was in the official MCP Registry list on 2026-10-23 (version 0.2.0 (published 2026-10-21)) and was not in the list on 2026-10-24. The registry gives no reason, and we do not guess one.

Everything below is the record we published from the 2026-10-23 snapshot. It is kept so existing links still work, and it is no longer updated.

MCP servers › dev.wagate › wagate

MCP server · registry snapshot 2026-10-23

dev.wagate/wagate

Read WhatsApp chats and groups, and send messages when allowed, through the WaGate API. — the publisher's description

3 of 6 record checks metTopic: communication-and-social · AI-classifiedPricing: freemium · AI-classifiedversion 0.2.0MITstandard input/output

Summary

dev.wagate/wagate is a local MCP server listed in the official MCP registry at version 0.2.0.

Record checks

3 of 6 record checks met · 3 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: 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)
not met: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version current
License: MIT
Dependencies: 2 packages with a critical or high advisory (0 critical, 2 high)
Topic: communication-and-socialAI-classified
Pricing: freemiumAI-classified
Last tested: not tested

Add to your client

Worth knowing before you connect it

2 packages with a critical or high advisory (0 critical, 2 high) in its dependencies (as resolved on 2026-10-24).

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.2.0, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-21 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-22

What it is

How do I add it to my client?

Config from the registry entry

From the npm package @wagate/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": {
    "wagate": {
      "command": "npx",
      "args": [
        "-y",
        "@wagate/mcp@0.2.0"
      ],
      "env": {
        "GATEWAY_API_TOKEN": "<GATEWAY_API_TOKEN>",
        "GATEWAY_CHANNEL_ID": "<GATEWAY_CHANNEL_ID>"
      }
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "wagate": {
      "command": "npx",
      "args": [
        "-y",
        "@wagate/mcp@0.2.0"
      ],
      "env": {
        "GATEWAY_API_TOKEN": "<GATEWAY_API_TOKEN>",
        "GATEWAY_CHANNEL_ID": "<GATEWAY_CHANNEL_ID>"
      }
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "wagate": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@wagate/mcp@0.2.0"
      ],
      "env": {
        "GATEWAY_API_TOKEN": "${input:gateway-api-token}",
        "GATEWAY_CHANNEL_ID": "${input:gateway-channel-id}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "gateway-api-token",
      "description": "GATEWAY_API_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "gateway-channel-id",
      "description": "GATEWAY_CHANNEL_ID",
      "password": false
    }
  ]
}

Claude Code

claude mcp add --env "GATEWAY_API_TOKEN=<GATEWAY_API_TOKEN>" "GATEWAY_CHANNEL_ID=<GATEWAY_CHANNEL_ID>" --transport stdio wagate -- npx -y @wagate/mcp@0.2.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -e "GATEWAY_API_TOKEN=<GATEWAY_API_TOKEN>" -e "GATEWAY_CHANNEL_ID=<GATEWAY_CHANNEL_ID>" -- npx -y @wagate/mcp@0.2.0

Replace <GATEWAY_API_TOKEN>, <GATEWAY_CHANNEL_ID> with your own values; the entry marks GATEWAY_API_TOKEN as secret, so keep the file out of version control.
Optional settings the entry also lists (left out above): GATEWAY_ALLOW_SEND, GATEWAY_API_URL.
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). 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.2.0
Latest stable: 0.2.0
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. 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-10-24 (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-yuBHqhKjPbPdtYxVt…
Signature: signed
License: MIT

Source: the package registry · 2026-10-22.

Usage

Downloads: 216 in the last month

Source: api.npmjs.org · 2026-10-22.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Version 0.2.0 on npm	Exists and can be installed	matches	npm · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

3 of 6 record checks met · 3 do not apply

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
Not metNo known critical or high advisory in the package or its dependencies2 packages in its dependencies with a critical or high advisory (npm audit counts packages, not advisories).

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. 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. How each check works · Leaderboards

Common questions about dev.wagate/wagate

Answered from the data above

Is dev.wagate/wagate safe to install?

We do not rate servers as safe or unsafe. 3 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has packages with advisories (2 high; npm audit). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is dev.wagate/wagate free to use?

Its website (wagate.dev/docs/mcp) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has dev.wagate/wagate been security tested?

Not yet. 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.

Is the listed version current?

Yes. The registry lists 0.2.0, the latest stable release on npm.

Security testing

Has it been tested?

Feature #1

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. — the server's own choice

Required inputs the publisher declares: GATEWAY_API_TOKEN (secret), GATEWAY_CHANNEL_ID.

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.

TopicAI-classified

communication-and-social

AI-classified · 2026-10-23

Pricing modelAI-classified

freemium

read from wagate.dev/docs/mcp · 2026-10-23

“HelloHop is an independent WhatsApp API for developers: send and receive messages, automate groups and communities, and get signed webhooks, from $25 per number per month with a free sandbox.”

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

local package

registry · 2026-10-23

MCP capability

not checked

not read (no session)

Transport

standard input/output

registry · 2026-10-23

Required credentials

requires a secret

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-22

Integrity hash

declared (sri)

package registry · 2026-10-22

Signature / provenance

signed

package registry · 2026-10-22

Dependency advisories

high

npm audit · 2026-10-24

Popularity

216 downloads a month

package registry · 2026-10-22

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

your machine

where it runs, from the hosting type

“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. “dev.wagate/wagate: MCP server record.” Data checked 2026-10-22. https://protocolprobe.com/mcp/servers/dev.wagate/wagate

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.

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.

Write to hello@protocolprobe.com · corrections log · methodology