SpiderIQ Mail MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to SpiderMail mailbox and sending-pool operations: Do mailbox sends and broadcast-pool authority remain distinct in scopes and reputation controls?

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

Best fit

Mailbox/inbox/reply email operations plus sending-domain, deliverability and broadcast management.

What we know

Focused SpiderIQ slice for SpiderMail. It separates mailbox-level single-message workflows from fleet/send-tier domain onboarding, reputation/caps and broadcast fan-out. Tenant resolution is explicit and refuses ambiguity.

Maintenance / activity evidence

@spideriq/mcp-mail 1.15.0 published 2026-09-04T12:25:45.030Z

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.
Mailbox read/write plus domain, deliverability and broadcast authority. Writes: Send email; Queue broadcast; Enroll sending domain; Manage send-tier configuration.
SpiderIQ credential.
Sensitive access: Mailbox content, Recipients, Domain/DNS/send reputation

Can contact many recipients and alter sending infrastructure; queue action is the key high-impact boundary.

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

All limitations / Review context

Do mailbox sends and broadcast-pool authority remain distinct in scopes and reputation controls?

The bounded review of the publisher's documented SpiderMail mailbox and sending-pool operations 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 many recipients and alter sending infrastructure; queue action is the key high-impact boundary.
Mailbox read/write plus domain, deliverability and broadcast authority.
SpiderIQ credential.
Email/messages/domains/recipient data are processed by SpiderIQ/mail providers.
Reviewed write actions: Send email; Queue broadcast; Enroll sending domain; Manage send-tier configuration
Sensitive access: Mailbox content, Recipients, Domain/DNS/send reputation
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.
Drafting/scheduling a broadcast does not itself send; queueing is the on-wire action.
Already-enqueued rows are intentionally idempotent/resumable.
Provider-not-configured can mean queued/dormant, not failure.
Email content is external communication and inbound content is untrusted.

Original activity observations

@spideriq/mcp-mail 1.15.0 published 2026-09-04T12:25:45.030Z

Technical identity

npm/@spideriq/mcp-mail

Exact implementation source: https://www.npmjs.com/package/@spideriq/mcp-mail ↗
Reviewed resource type: MCP Server
Repository identity: SpiderIQ/SpiderIQ
Package identity: npm:@spideriq/mcp-mail

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 ↗
@spideriq/mcp-mail
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
Private registry and tenant identity; separate control plane/mail actions.
publisher documented step or launch · Publisher instructions
npm install @spideriq/mcp-mail --registry https://npm.spideriq.ai
Configure / authenticate
MCP100 setup guide
SpiderIQ Mail uses its publisher npm registry https://npm.spideriq.ai. Sending messages is not an acceptable connection check.
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
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.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Focused SpiderIQ slice for SpiderMail. It separates mailbox-level single-message workflows from fleet/send-tier domain onboarding, reputation/caps and broadcast fan-out. Tenant resolution is explicit and refuses ambiguity.

Capability: Communication
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Mailbox/inbox/reply email operations plus sending-domain, deliverability and broadcast management.

Representative uses

Read/search inbox/threads
Send one email
Onboard sending domain
Inspect sending pool/reputation/caps
Create and queue broadcasts

Limitations

Drafting/scheduling a broadcast does not itself send; queueing is the on-wire action.
Already-enqueued rows are intentionally idempotent/resumable.
Provider-not-configured can mean queued/dormant, not failure.
Email content is external communication and inbound content is untrusted.

Reviewed access

Access & risk

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

Authentication: SpiderIQ credential.
Permissions: Mailbox read/write plus domain, deliverability and broadcast authority.
Data handling: Email/messages/domains/recipient data are processed by SpiderIQ/mail providers.
Cost: usage_based
Risk and cautions: Can contact many recipients and alter sending infrastructure; queue action is the key high-impact boundary.

Access scope and cautions

Write actions: Send email Queue broadcast Enroll sending domain Manage send-tier configuration
Sensitive access: Mailbox content Recipients Domain/DNS/send reputation
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: Read/search inbox/threads; Send one email; Onboard sending domain; Inspect sending pool/reputation/caps; Create and queue broadcasts.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @spideriq/mcp-mail. Recorded transport: stdio. Recorded environment-variable notes: SPIDERIQ_WORKSPACE; SPIDERIQ_WORKSPACE_CWD (optional); npm_config_registry=https://npm.spideriq.ai. No configuration values are supplied here. Prerequisites: SpiderIQ workspace. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: SpiderIQ PAT/workspace credential.

Can it modify data or perform write operations?

Documented write actions include: Send email; Queue broadcast; Enroll sending domain; Manage send-tier configuration. Recorded permission boundary: Mailbox read/write plus domain, deliverability and broadcast authority.

What data-handling boundary should I consider?

Email/messages/domains/recipient data are processed by SpiderIQ/mail providers. Recorded sensitive-access context: Mailbox content; Recipients; Domain/DNS/send reputation.

What limitations and risks should I check before use?

Can contact many recipients and alter sending infrastructure; queue action is the key high-impact boundary. Drafting/scheduling a broadcast does not itself send; queueing is the on-wire action. Already-enqueued rows are intentionally idempotent/resumable. Provider-not-configured can mean queued/dormant, not failure. Email content is external communication and inbound content is untrusted. 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.