SendRaven MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to SendRaven email threads, campaigns and approval tools: Do recipient allowlists, approval holds and daily limits remain enforced for both single sends and campaigns?

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

Best fit

Email sending, inbound-thread handling and campaigns with agent-specific guardrails.

What we know

Email infrastructure MCP available remotely with OAuth or locally with an API key, covering messages, replies, contacts, campaigns, templates, automations, suppressions and approvals.

Maintenance / activity evidence

@sendraven/mcp 0.4.21 published 2026-10-05T14:06:08.174Z

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.
Credential-scoped access to email, contacts, campaigns, templates, domains, suppressions and approvals. Writes: Send/reply/schedule/cancel email; Start/pause/resume campaigns; Modify contacts/suppressions/templates/automations; Approve held sends.
OAuth or bearer API key.
Sensitive access: Email content, Recipient/contact data, Delivery events, Domain/email configuration

Can contact real people and run campaigns; human approval, allowlists and caps materially reduce risk.
Inbound email should be treated as untrusted data.
API-key guardrails and idempotency are documented.

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

All limitations / Review context

Do recipient allowlists, approval holds and daily limits remain enforced for both single sends and campaigns?

The bounded review of the publisher's documented SendRaven email threads, campaigns and approval tools 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.

Can contact real people and run campaigns; human approval, allowlists and caps materially reduce risk.
Inbound email should be treated as untrusted data.
API-key guardrails and idempotency are documented.
Credential-scoped access to email, contacts, campaigns, templates, domains, suppressions and approvals.
OAuth or bearer API key.
Email bodies, recipients, delivery events, replies and contacts pass through SendRaven; detailed retention was not fully established.
Reviewed write actions: Send/reply/schedule/cancel email; Start/pause/resume campaigns; Modify contacts/suppressions/templates/automations; Approve held sends
Sensitive access: Email content, Recipient/contact data, Delivery events, Domain/email configuration
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.
detailed retention/deletion policy for email/contact data
Sending requires appropriate account/domain setup and payment eligibility.
Campaign and suppression/contact changes can be consequential.
Remote OAuth does not inherit every API-key guardrail such as recipient allowlists/daily caps/approval hold.
Tool registry can evolve.

Original activity observations

@sendraven/mcp 0.4.21 published 2026-10-05T14:06:08.174Z

Technical identity

npm/@sendraven/mcp

Exact implementation source: https://www.npmjs.com/package/@sendraven/mcp ↗
Reviewed resource type: MCP Server
Repository identity: CommonNinja/sendraven-mcp-server
Package identity: npm:@sendraven/mcp
Service endpoint: https://mcp.sendraven.ai/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 ↗
@sendraven/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
sendraven.ai/docs/mcp
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
sendraven.ai/docs/agents
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
sendraven.ai/pricing
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
commonninja/sendraven-mcp-server
Repository reference; implementation attribution is not established for every document.
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.

Install / connect
Publisher instructions
Remote OAuth is publisher route; local `npx -y @sendraven/mcp` needs API key. Message drafting and approval/sending are separate; human approval must not be bypassed.
Publisher supports OAuth remote endpoint and local `claude mcp add sendraven -e SENDRAVEN_API_KEY=<key> -- npx -y @sendraven/mcp`; use one auth route, not both.
publisher documented install or connect · Publisher instructions
claude mcp add sendraven -e SENDRAVEN_API_KEY=<your-key> -- npx -y @sendraven/mcp
Configure / authenticate
MCP100 setup guide
Local stdio uses SENDRAVEN_API_KEY. Remote endpoint uses OAuth and is a different connection choice. Do not test by sending email or launching a campaign.
remote_streamable_http: https://mcp.sendraven.ai/mcp
Environment variables referenced by this route (respect the alternatives above): SENDRAVEN_API_KEY
Remote client registration · Publisher instructions
claude mcp add --transport http sendraven https://mcp.sendraven.ai/mcp
Check connection
Suggested check
After authentication, inspect read-only messaging metadata or list threads using the publisher-exposed tools; do not send a test email or start a campaign.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
If API-key mode is used, revocation must be done in SendRaven account controls; exact UI revocation action not established from the reviewed package README.

Official Documentation & Sources

What it does

Email infrastructure MCP available remotely with OAuth or locally with an API key, covering messages, replies, contacts, campaigns, templates, automations, suppressions and approvals.

Capability: Communication
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Email sending, inbound-thread handling and campaigns with agent-specific guardrails.

Representative uses

Send or schedule transactional/template email
Read inbound threads and reply
Create/preview/schedule/send campaigns
Manage contacts, audiences, suppressions, templates and automations
Hold agent sends for human approval

Limitations

Sending requires appropriate account/domain setup and payment eligibility.
Campaign and suppression/contact changes can be consequential.
Remote OAuth does not inherit every API-key guardrail such as recipient allowlists/daily caps/approval hold.
Tool registry can evolve.

Reviewed access

Access & risk

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

Authentication: OAuth or bearer API key.
Permissions: Credential-scoped access to email, contacts, campaigns, templates, domains, suppressions and approvals.
Data handling: Email bodies, recipients, delivery events, replies and contacts pass through SendRaven; detailed retention was not fully established.
Cost: freemium
Risk and cautions: Can contact real people and run campaigns; human approval, allowlists and caps materially reduce risk.

Access scope and cautions

Write actions: Send/reply/schedule/cancel email Start/pause/resume campaigns Modify contacts/suppressions/templates/automations Approve held sends
Sensitive access: Email content Recipient/contact data Delivery events Domain/email configuration
Risk level: high
Security notes: Inbound email should be treated as untrusted data. API-key guardrails and idempotency are documented.

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: Send or schedule transactional/template email; Read inbound threads and reply; Create/preview/schedule/send campaigns; Manage contacts, audiences, suppressions, templates and automations; Hold agent sends for human approval.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @sendraven/mcp. Recorded endpoint: https://mcp.sendraven.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: SENDRAVEN_API_KEY (local); SENDRAVEN_API_URL (optional); PORT (optional). No configuration values are supplied here. Prerequisites: MCP client; SendRaven workspace; verified sending setup for outbound mail. Client notes: For autonomous use prefer constrained API keys with daily cap/recipient allowlist/approval hold. Use idempotency keys for safe retries. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Remote OAuth or bearer API key; local stdio uses `SENDRAVEN_API_KEY`.

Can it modify data or perform write operations?

Documented write actions include: Send/reply/schedule/cancel email; Start/pause/resume campaigns; Modify contacts/suppressions/templates/automations; Approve held sends. Recorded permission boundary: Credential-scoped access to email, contacts, campaigns, templates, domains, suppressions and approvals.

What data-handling boundary should I consider?

Email bodies, recipients, delivery events, replies and contacts pass through SendRaven; detailed retention was not fully established. Recorded sensitive-access context: Email content; Recipient/contact data; Delivery events; Domain/email configuration.

What limitations and risks should I check before use?

Can contact real people and run campaigns; human approval, allowlists and caps materially reduce risk. Sending requires appropriate account/domain setup and payment eligibility. Campaign and suppression/contact changes can be consequential. Remote OAuth does not inherit every API-key guardrail such as recipient allowlists/daily caps/approval hold. Tool registry can evolve. Inbound email should be treated as untrusted data. API-key guardrails and idempotency are documented. 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.

Is this an official MCP?

SendRaven / Common Ninja is listed as First-party MCP in MCP100’s current evidence.