SpamTitan
OCI · GHCR.IO/WYRE-TECHNOLOGY/SPAMTITAN-MCP:V1.3.2
MCP server for SpamTitan email security — quarantine, allow/block lists, and policy management.
Available components
Last scanned (4 hours ago)
Scores higher than 82% of OCI servers
Category Security
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. 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 (Apache-2.0).Pass
- Actively maintained (last published 70 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 776 tokens (~77/item across 10 items; 9 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 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
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −3
- Source repository: unverified → fail ▼ security
- 10 Oct 26 0
- Provenance: fail → unverified ▼ security
- Stability: pass → 0.97 functional
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 17 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/spamtitan-mcp:v1.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
spamtitan_delete_message ~68
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently delete a quarantined message by ID. This action cannot be undone and will remove the message from quarantine storage. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The quarantined message ID to delete |
No output schema declared.
No examples provided.
spamtitan_get_message ~62
Get a single quarantined message by ID. Returns sender, recipient, subject, quarantine reason, spam score, and status. Renders as an interactive card in MCP Apps hosts.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The quarantined message ID to fetch |
No output schema declared.
No examples provided.
spamtitan_get_queue ~129
List the email quarantine queue. Returns quarantined messages with sender, recipient, subject, and reason for quarantine.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination (default: 1) |
| per_page | number | – | Number of results per page (default: 50, max: 200) |
| reason | string | – | Filter by quarantine reason (e.g. spam, virus, policy) |
| recipient | string | – | Filter by recipient email address |
| sender | string | – | Filter by sender email address |
| subject | string | – | Filter by subject (partial match) |
No output schema declared.
No examples provided.
spamtitan_get_stats ~66
Get email flow statistics from SpamTitan including messages received, blocked, quarantined, and delivered. Supports filtering by time period.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Filter statistics for a specific domain (optional) |
| period | string | – | Time period for statistics (default: today) |
No output schema declared.
No examples provided.
spamtitan_manage_allowlist ~117
Add or remove sender allowlist entries in SpamTitan. Allowlisted senders always bypass spam filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: 'add' to allowlist a sender, 'remove' to remove one, 'list' to view all entries |
| note | string | – | Optional note explaining why this entry was added (for add action) |
| sender | string | – | Sender email address or domain to add/remove (e.g. user@example.com or @example.com). Required for add/remove actions. |
No output schema declared.
No examples provided.
spamtitan_manage_blocklist ~153
⚠ HIGH-IMPACT. Add or remove sender blocklist entries in SpamTitan. Modifies email delivery policy and affects deliverability for users. Blocklisted senders are always rejected or quarantined. Reversible by removing entries. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: 'add' to blocklist a sender, 'remove' to remove one, 'list' to view all entries |
| note | string | – | Optional note explaining why this entry was added (for add action) |
| sender | string | – | Sender email address or domain to add/remove (e.g. spammer@evil.com or @evil.com). Required for add/remove actions. |
No output schema declared.
No examples provided.
spamtitan_navigate ~104
Discover available SpamTitan tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to explore: - quarantine: Email quarantine management - list queue, release and delete quarantined messages - lists: Allowlist/blocklist management - manage email filtering rules - stats:… |
No output schema declared.
No examples provided.
spamtitan_release_message ~41
Release a quarantined message by ID, delivering it to the intended recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The quarantined message ID to release |
No output schema declared.
No examples provided.
spamtitan_status ~17
Show credentials status and available domains
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SpamTitan MCP server?
SpamTitan runs locally as a container image, launched with docker run --rm -i -e SPAMTITAN_API_URL -e SPAMTITAN_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/spamtitan-mcp:v1.3.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-technology/spamtitan-mcp:v1.3.2
claude mcp add wyre-technology-spamtitan-mcp -- docker run --rm -i -e SPAMTITAN_API_URL -e SPAMTITAN_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/spamtitan-mcp:v1.3.2
This image reads SPAMTITAN_API_URL, SPAMTITAN_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the SpamTitan MCP server?
SpamTitan is an MCP server listed in the public MCP registry as io.github.wyre-technology/spamtitan-mcp. MCP server for SpamTitan email security, quarantine, allow/block lists, and policy management. This page covers its container image (ghcr.io/wyre-technology/spamtitan-mcp:v1.3.2).
Is the SpamTitan MCP server safe to use?
SpamTitan scores 51 out of 100 on VerifyMCP. 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 SpamTitan MCP server expose?
SpamTitan exposes 9 tools: spamtitan_navigate, spamtitan_status, spamtitan_get_queue, spamtitan_get_message, spamtitan_release_message, and 4 more. Their descriptions and schemas cost roughly 757 tokens of context every time the server is loaded.
Is the SpamTitan MCP server still maintained?
SpamTitan is still listed as active in the MCP registry. We last reached this channel on 17 October 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 SpamTitan MCP server under?
SpamTitan declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.