Security review

Is brainCloud MCP Helper MCP safe to give an agent?

destructive capableneeds cautiondestructive capablehealthy

A factual risk summary built from brainCloud MCP Helper’s real tool surface, execution model, and verification history — not a vibe. Trust score 72/100.


01What it can do

Has tools that can delete or irreversibly change data.

4 tools observeddestructive presentwrite present

02Execution model

Runs locally over stdio — the server process executes on your machine with your user's privileges. Vet the source and package before granting access.

Installs via npx (`npx -y @braincloud/mcp-helper@latest`) — it pulls and executes third-party code; pin versions and review the source.


03Permissions & auth

No write or destructive access inferred from this server’s tools yet. Absence of a scope isn’t a guarantee — treat unconfirmed access as unknown, not “none.”


04Verification
handshakepassed — tool surface is real
runstools_list:passed · handshake:passed · metadata:passed
last_checked2026-07-10 21:21Z
sourcesOfficial MCP Registry [p1]

Reduce the risk

Worried about handing an agent raw access? See governed agents in action — Apex gives your AI paced, capped, fully-logged hands with approval queues before anything runs.

Explore Apex →

See also: full server page · setup · alternatives

Is brainCloud MCP Helper MCP safe? — risk & permissions — MCPExplorer