Ararahq MCP Server

ararahq-mcp npm v4.2.1

Published by ararahq — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for AraraHQ — turn Claude Code, Claude Desktop, Cursor, Windsurf or ChatGPT into a WhatsApp operator. Say who and what: send_whatsapp, broadcast and check_status do the heavy lifting (number, E.164, 24h window, template) for you.

Trust grade
B
87/100
Last scanned get badge →
Trust
B · 87/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 94 − adoption risk = 87/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Description names a credential store the tool cannot reach MTC-INJ-SCHEMA-1 injection

2. Client adoption risk — 94 − 7 = 87. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (build/lib/deviceFlow.js)MTC-SRC-002

In the server's implementation (`build/lib/deviceFlow.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from "node:child_process"; import { extractError } from "./api.js"; import { ARARA_BASE, OAUTH_CLIENT_ID, O

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/lib/deviceFlow.js

medium Description names a credential store the tool cannot reachMTC-INJ-SCHEMA-1

Tool "logout" describes a credential store (SSH keys, cloud credentials, a keychain or an equivalent) that nothing in its input schema can address. A tool's interface is the honest statement of what it touches; prose that reaches past it is addressed to the model, not to a reader.

Evidence: keychain

Fix: Remove the reference, or expose the target as an explicit, validated parameter so the client can see and consent to what the tool reads.

Location: tool logout · description

Tools 19

Each tool and what it can reach — statically extracted from the published source.

  • broadcastno sensitive capability
  • broadcast_abno sensitive capability
  • check_statusno sensitive capability
  • create_short_linkno sensitive capability
  • create_smart_linkno sensitive capability
  • create_templateno sensitive capability
  • get_campaignno sensitive capability
  • get_template_statusno sensitive capability
  • list_campaignsno sensitive capability
  • list_short_linksno sensitive capability
Show 9 more tools ↓
  • list_smart_linksno sensitive capability
  • loginno sensitive capability
  • logoutno sensitive capability
  • opt_outno sensitive capability
  • read_conversationno sensitive capability
  • save_contactsno sensitive capability
  • send_templateno sensitive capability
  • send_whatsappno sensitive capability
  • whoamino sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v4.2.1 latest B 87/100 2 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 87/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ararahq-mcp/badge.svg)](https://mcptrustchecker.com/registry/ararahq-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ararahq-mcp"><img src="https://mcptrustchecker.com/registry/ararahq-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ararahq-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ararahq-mcp --online

Use the free API → How scoring works

More in Developer Tools