Cadence RCS MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Cadence RCS messaging with SMS fallback: Do sandbox delivery, live sends and fallback status remain distinguishable when carrier onboarding changes?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Agent-native RCS conversations with branded SMS fallback, reply handling and guarded irreversible onboarding actions.

What we know

Cadence MCP lets agents open conversations, send/respond over RCS with SMS fallback, inspect/close conversations and guide brand/carrier onboarding. Irreversible go-live actions require both an environment opt-in and explicit per-call confirmation.

Maintenance / activity evidence

@cadencercs/mcp 0.3.1 published 2026-08-25T23:41:08.090Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Send/receive messaging plus onboarding/lifecycle actions. Writes: Send RCS/SMS; Open/close conversations; Irreversible production/onboarding actions when double-confirmed.
Cadence API key.
Sensitive access: Phone numbers, Message content, Carrier onboarding data

External communication plus explicitly irreversible actions require user/operator controls.
Irreversible operations are intentionally double-gated.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do sandbox delivery, live sends and fallback status remain distinguishable when carrier onboarding changes?

The bounded review of the publisher's documented Cadence RCS messaging with SMS fallback and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

External communication plus explicitly irreversible actions require user/operator controls.
Send/receive messaging plus onboarding/lifecycle actions.
Cadence API key.
Recipient phone/message/reply data is processed by Cadence/carrier channels.
Reviewed write actions: Send RCS/SMS; Open/close conversations; Irreversible production/onboarding actions when double-confirmed
Sensitive access: Phone numbers, Message content, Carrier onboarding data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Messaging can contact real recipients and incur carrier/service costs.
Docs briefly lagged package distribution status; npm package is now published.
Irreversible operations are intentionally double-gated.
Carrier availability and SMS fallback affect delivery behavior.
Official docs had a stale 'not published yet' note while npm package is live; prefer current package state but preserve doc drift.

Original activity observations

@cadencercs/mcp 0.3.1 published 2026-08-25T23:41:08.090Z

Technical identity

npm/@cadencercs/mcp

Exact implementation source: https://www.npmjs.com/package/@cadencercs/mcp ↗
Reviewed resource type: MCP Server
Repository identity: dwixom/rcs-agent-mvp
Package identity: npm:@cadencercs/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@cadencercs/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
cadencercs.com/docs.html
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Publisher mcpServers JSON requires CADENCE_API_KEY; sandbox and live keys differ. Check irreversible operations section before enabling writes.
Use sandbox first; avoid irreversible live operations as verification.
Earlier review note retained for provenance; the V3 verified fields take precedence: Targeted 2026-10-13 re-research: Publisher mcpServers entry requires CADENCE_API_KEY; irreversible actions disabled unless CADENCE_ALLOW_IRREVERSIBLE=1.
Publisher mcpServers entry requires CADENCE_API_KEY; irreversible actions disabled unless CADENCE_ALLOW_IRREVERSIBLE=1.
MCP100 normalized publisher npm README command/config; placeholders are NOT real secrets; no client/runtime validation.
Prior reviewed safety note: Do not place orders, spend tokens, modify infrastructure or upload confidential files as a test.
Prior reviewed safety note: Do not invent a one-line reversal command.
Earlier review note retained for provenance; the V3 verified fields take precedence: Second-pass 2026-10-14 could not retrieve full current publisher npm README; preserve baseline, do not promote source-specific claims or run commands until documentation is rechecked.
Direct npm README reviewed 2026-10-14; client registration still required.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.

Install / connect
Publisher instructions
Publisher mcpServers JSON requires CADENCE_API_KEY; sandbox and live keys differ. Check irreversible operations section before enabling writes.
publisher documented mcp stdio launch · Publisher instructions
npx -y @cadencercs/mcp
Configure / authenticate
MCP100 setup guide
Configure MCP stdio `npx -y @cadencercs/mcp` with mandatory `CADENCE_API_KEY` in host env; use sandbox credentials when testing.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "cadence": { "args": [ "-y", "@cadencercs/mcp" ], "command": "npx", "env": { "CADENCE_API_KEY": "YOUR_CADENCE_API_KEY" } } } }
Check connection
Suggested check
Use `cadence_check_consent` or an account read tool; do not send an RCS message or create a brand in a connection check.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `cadencercs-mcp`, run `claude mcp remove cadencercs-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove cadencercs-mcp

Official Documentation & Sources

What it does

Cadence MCP lets agents open conversations, send/respond over RCS with SMS fallback, inspect/close conversations and guide brand/carrier onboarding. Irreversible go-live actions require both an environment opt-in and explicit per-call confirmation.

Capability: Communication
Resource type: MCP Server
Industry: Telecommunications
Best fit: Agent-native RCS conversations with branded SMS fallback, reply handling and guarded irreversible onboarding actions.

Representative uses

Open/send/close RCS/SMS conversations
Handle typed/chip replies
Get sandbox key/onboarding guidance
Preview and confirm irreversible production onboarding actions

Limitations

Messaging can contact real recipients and incur carrier/service costs.
Docs briefly lagged package distribution status; npm package is now published.
Irreversible operations are intentionally double-gated.
Carrier availability and SMS fallback affect delivery behavior.
Official docs had a stale 'not published yet' note while npm package is live; prefer current package state but preserve doc drift.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Cadence API key.
Permissions: Send/receive messaging plus onboarding/lifecycle actions.
Data handling: Recipient phone/message/reply data is processed by Cadence/carrier channels.
Cost: usage_based
Risk and cautions: External communication plus explicitly irreversible actions require user/operator controls.

Access scope and cautions

Write actions: Send RCS/SMS Open/close conversations Irreversible production/onboarding actions when double-confirmed
Sensitive access: Phone numbers Message content Carrier onboarding data
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Open/send/close RCS/SMS conversations; Handle typed/chip replies; Get sandbox key/onboarding guidance; Preview and confirm irreversible production onboarding actions.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @cadencercs/mcp. Recorded transport: stdio. Recorded environment-variable notes: CADENCE_API_KEY; CADENCE_API_URL (optional); CADENCE_ALLOW_IRREVERSIBLE (optional, off by default). No configuration values are supplied here. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Cadence sandbox/live API key.

Can it modify data or perform write operations?

Documented write actions include: Send RCS/SMS; Open/close conversations; Irreversible production/onboarding actions when double-confirmed. Recorded permission boundary: Send/receive messaging plus onboarding/lifecycle actions.

What data-handling boundary should I consider?

Recipient phone/message/reply data is processed by Cadence/carrier channels. Recorded sensitive-access context: Phone numbers; Message content; Carrier onboarding data.

What limitations and risks should I check before use?

External communication plus explicitly irreversible actions require user/operator controls. Messaging can contact real recipients and incur carrier/service costs. Docs briefly lagged package distribution status; npm package is now published. Irreversible operations are intentionally double-gated. Carrier availability and SMS fallback affect delivery behavior. Official docs had a stale 'not published yet' note while npm package is live. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.