ai.spideriq/mail
NPM · @SPIDERIQ/MCP-MAIL
SpiderIQ Mail: SpiderMail mailboxes, messages, threads, send, compose for AI agents
Available components
Last scanned (23 hours ago)
Scores higher than 45% of npm servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4522 tokens (~77/item across 58 items; 58 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logout" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@spideriq/mcp-mail@1.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 30 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
snooze_message ~68
Hide a message from the inbox until an ISO-8601 timestamp, then auto-return it.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | Numeric message id |
| snoozed_until | string | yes | ISO-8601 timestamp to unsnooze at |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
sync_outreach_connection ~61
Pull latest sender accounts + warmup state from the provider into SpiderMail. BRAND-ADMIN only.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Numeric brand id |
| connection_id | string | yes | Outreach connection id |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
test_mailbox ~41
Test a mailbox connection (IMAP/SMTP).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Mailbox email address to test | |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
unsnooze_message ~43
Cancel a snooze — return the message to the inbox now.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | Numeric message id |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
update_label ~59
Rename or recolour a label definition.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | New hex colour #RRGGBB |
| label_id | string | yes | Label id |
| name | string | – | New name |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
update_message ~102
Update a message flags — mark read/unread, star, set labels (labels REPLACE the set), private note.
| Name | Type | Req | Description |
|---|---|---|---|
| is_read | boolean | – | Mark read/unread |
| is_starred | boolean | – | Star/unstar |
| labels | array | – | Replace the label set with this list |
| message_id | string | yes | Numeric message id |
| notes | string | – | Private note (not sent) |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
update_outreach_connection ~196
Edit an outreach connection (workspace_id / warmup_tag / lemwarm_domains / is_active / smartlead_client_id / max_active_leads). BRAND-ADMIN only.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Numeric brand id |
| connection_id | string | yes | Outreach connection id |
| is_active | boolean | – | Enable/pause the sidecar |
| lemwarm_domains | array | – | lemlist warmup domains |
| max_active_leads | number | – | Cap on distinct leads pushed via this connection (mirrors the SmartLead account lead-credit ceiling); 0+ or omit for uncapped |
| smartlead_client_id | string | – | SmartLead agency/whitelabel client id (scopes shared-account campaigns); empty string clears it |
| warmup_tag | string | – | Tag marking warmup sends |
| workspace | string | – | Workspace name |
| workspace_id | string | – | Provider workspace id |
No output schema declared.
No examples provided.
update_view ~97
Edit a saved view (creator-only).
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | New colour |
| filter_config | object | – | New filter config |
| is_shared | boolean | – | Share with the team |
| name | string | – | New name |
| sort_by | string | – | Sort field |
| sort_direction | string | – | Sort direction |
| view_id | string | yes | Saved view id |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
How do I install the ai.spideriq/mail MCP server?
ai.spideriq/mail runs locally as an npm package, launched with npx -y @spideriq/mcp-mail. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @spideriq/mcp-mail
claude mcp add ai-spideriq-mail -- npx -y @spideriq/mcp-mail
What is the ai.spideriq/mail MCP server?
ai.spideriq/mail is an MCP server listed in the public MCP registry as ai.spideriq/mail. SpiderIQ Mail: SpiderMail mailboxes, messages, threads, send, compose for AI agents. This page covers its npm package (@spideriq/mcp-mail).
Is the ai.spideriq/mail MCP server safe to use?
ai.spideriq/mail scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.spideriq/mail MCP server expose?
ai.spideriq/mail exposes 58 tools: request_access, check_access_status, get_auth_status, logout, list_workspaces, and 53 more. Their descriptions and schemas cost roughly 4,522 tokens of context every time the server is loaded.
Is the ai.spideriq/mail MCP server still maintained?
ai.spideriq/mail is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ai.spideriq/mail MCP server under?
ai.spideriq/mail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.