uni-msg-mcp-server

MCPcommunitylive
v0.3.1com.uni-msgMITUpdated 1mo agonpmGitHub

Drive WhatsApp from any MCP client: pair devices, send text and media, manage contacts and groups.

Endpoint healthlive
checked 8 days ago · 297ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
120Downloads/wk
1mo agoLast update
Needs 1 credential before it runs
  • UNIMSG_API_KEYAPI keyrequired

    API key from uni-msg Dashboard → API Keys (starts with wsa_)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorcom.uni-msg
LicenseMIT
Version0.3.1
Sourcenpm+mcp-registry
npmuni-msg-mcp-server
GitHuboneorco/onemsg
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface13 tools · none privileged
Security scan✓ Cleanv0.3.1 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 25, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

13 tools · none privileged
Statically extracted from the published packagev0.3.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_devicesList the WhatsApp devices on this account with their connection status.

List the WhatsApp devices on this account with their connection status.

No input schema was published for this tool.

get_device_statusCheck one device: whether it is connected, and when it was last seen.

Check one device: whether it is connected, and when it was last seen.

No input schema was published for this tool.

create_deviceRegister a new WhatsApp number so it can be paired. Step 1 of 3:

Register a new WhatsApp number so it can be paired. Step 1 of 3:

No input schema was published for this tool.

connect_deviceStep 2 of 3. Starts a session and returns an 8-character pairing code

Step 2 of 3. Starts a session and returns an 8-character pairing code

No input schema was published for this tool.

request_pairing_codeIssue a fresh pairing code for a device that is already connecting. Use

Issue a fresh pairing code for a device that is already connecting. Use

No input schema was published for this tool.

disconnect_deviceEnd a device session. The number stays registered and can be reconnected

End a device session. The number stays registered and can be reconnected

No input schema was published for this tool.

send_messageSend a WhatsApp text message. The recipient may be a phone number in

Send a WhatsApp text message. The recipient may be a phone number in

No input schema was published for this tool.

send_mediaSend an image, video, audio clip or document by public URL. The URL must

Send an image, video, audio clip or document by public URL. The URL must

No input schema was published for this tool.

list_contactsList saved contacts, optionally filtered by a search term.

List saved contacts, optionally filtered by a search term.

No input schema was published for this tool.

upsert_contactCreate a contact, or update it if the number already exists. Matching is

Create a contact, or update it if the number already exists. Matching is

No input schema was published for this tool.

list_conversationsList recent WhatsApp conversations for a device — who has been in touch

List recent WhatsApp conversations for a device — who has been in touch

No input schema was published for this tool.

read_threadRead the message history with one contact or group. "peer" is the other

Read the message history with one contact or group. "peer" is the other

No input schema was published for this tool.

list_groupsList WhatsApp groups a device belongs to, with their JIDs. Use the JID as

List WhatsApp groups a device belongs to, with their JIDs. Use the JID as

No input schema was published for this tool.

13 of 13 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Drive WhatsApp from any MCP client: pair devices, send text and media, manage contacts and groups.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

13 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in chat & messaging