SentFromAI MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to SentFromAI email, inbox and filtering tools: Do allow/block rules and outbound authority remain explicit as mailbox and domain tools expand?

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

Best fit

AI-attributed outbound communication/integration under the SentFromAI product identity.

What we know

Radar identifies `sentfromai-mcp`, but first-party package/docs material sufficient to establish exact message channels, authentication, retention and write semantics was not recovered in this pass.

Maintenance / activity evidence

sentfromai-mcp 0.4.1 published 2026-09-30T01:56:35.711Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Potential recipient/message content

Communication tools can have external side effects; insufficient first-party evidence.

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

All limitations / Review context

Do allow/block rules and outbound authority remain explicit as mailbox and domain tools expand?

The bounded review of the publisher's documented SentFromAI email, inbox and filtering 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.

Communication tools can have external side effects; insufficient first-party evidence.
Unknown.
Sensitive access: Potential recipient/message content
Complete write authority is not verified.
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.
official docs/repository
channel/tool inventory
auth
retention
write actions
Exact channel (email/SMS/etc.), auth, delivery semantics and write actions unresolved.
Do not infer external-send authority beyond what the installed tool list proves.

Original activity observations

sentfromai-mcp 0.4.1 published 2026-09-30T01:56:35.711Z

Technical identity

npm/sentfromai-mcp

Exact implementation source: https://www.npmjs.com/package/sentfromai-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:sentfromai-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 ↗
sentfromai-mcp
Recorded package identity, distribution or download evidence.
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
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add sentfromai --env SENTFROMAI_API_KEY=sf_live_... -- npx -y sentfromai-mcp
Configure / authenticate
MCP100 setup guide
Alternatively hosted https://api.sentfrom.ai/mcp with OAuth/Bearer. Email sends are external side effects.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Check connection
Suggested check
Confirm email tools available with valid auth; use read-only list/status rather than sending an email.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `sentfromai-mcp` in Claude Code, remove its exact client entry with `claude mcp remove sentfromai-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Publisher install example registration name(s): sentfromai. The supplied removal example applies only to an existing Claude Code registration named sentfromai-mcp; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
```
claude mcp remove sentfromai-mcp
```

Official Documentation & Sources

What it does

Radar identifies `sentfromai-mcp`, but first-party package/docs material sufficient to establish exact message channels, authentication, retention and write semantics was not recovered in this pass.

Capability: Communication
Resource type: MCP Server
Best fit: AI-attributed outbound communication/integration under the SentFromAI product identity.

Representative uses

Use SentFromAI communication tools once configured

Limitations

Exact channel (email/SMS/etc.), auth, delivery semantics and write actions unresolved.
Do not infer external-send authority beyond what the installed tool list proves.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Unknown.
Cost: unknown
Risk and cautions: Communication tools can have external side effects; insufficient first-party evidence.

Access scope and cautions

Write actions: Not verified
Sensitive access: Potential recipient/message content
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

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: Use SentFromAI communication tools once configured.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What data-handling boundary should I consider?

Unknown. Recorded sensitive-access context: Potential recipient/message content.

What limitations and risks should I check before use?

Communication tools can have external side effects; insufficient first-party evidence. Exact channel (email/SMS/etc.), auth, delivery semantics and write actions unresolved. Do not infer external-send authority beyond what the installed tool list proves. 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.