dead-letter
OCI · GHCR.IO/BIGCACTUSLABS/DEAD-LETTER · 3 COMPONENTS
Convert .eml and .mbox email to clean Markdown for RAG, LLM pipelines, and local knowledge bases
Last scanned (12 hours ago)
Scores higher than 41% of OCI servers
Category Documents and Files
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 image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result. View diagnostics → Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (PolyForm-Noncommercial-1.0.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability42
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1267 tokens (~253/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 −4
- Stability: pass → 0.67 functional
- 29 Oct 26 0
- Package version: sha256:0023516c85b2e5464d7a73cf037289f43d4aa8f44f13dbb6f4e09f5b9f9fa8c7 → sha256:08699fa81fd5be51b12cdbcbbcdd4333f8a2dd9d928d79ca1b9e34473beac8af functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 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.
- 25 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.
- 23 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.
- 22 Oct 26 0
- Package version: sha256:ed4b3665a6d76362d9a1835fe6511c7906524acde3484331fa62998af6e1f30c → sha256:0023516c85b2e5464d7a73cf037289f43d4aa8f44f13dbb6f4e09f5b9f9fa8c7 functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 5 Nov 2026 · Analysed oci/ghcr.io/bigcactuslabs/dead-letter@sha256:08699fa81fd5be51b12cdbcbbcdd4333f8a2dd9d928d79ca1b9e34473beac8af
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 →
Vulnerabilities 12 ungraded findings
From the publisher's SBOM, not graded. These advisories match packages listed in the SBOM the publisher attached to this image. A publisher naming a vulnerable package in their own image is credible, so we show them. Nothing verifies that SBOM, though, so the Known CVEs signal does not grade the image from it.
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-4xh5-x5gv-qwph | CVE-2025-8869 | medium | yes | |
| GHSA-58qw-9mgm-455v | CVE-2026-3219 | medium | yes | |
| GHSA-6vgw-5pg2-w6jp | CVE-2026-1703 | low | yes | |
| GHSA-jp4c-xjxw-mgf9 | CVE-2026-6357 | medium | yes | |
| GHSA-qwm4-qh6w-59xr | CVE-2026-13346 | medium | yes | |
| GHSA-wf93-45jw-7689 | CVE-2026-8643 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-1795 | CVE-2025-8869 | none | yes | |
| PYSEC-2026-1796 | CVE-2026-1703 | none | yes | |
| PYSEC-2026-196 | CVE-2026-8643 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| PYSEC-2026-2875 | CVE-2026-3219 | none | yes | |
| PYSEC-2026-2876 | CVE-2026-6357 | none | yes | |
| PYSEC-2026-3721 | CVE-2026-13346 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
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 →
convert_directory Convert email folder ~240
Batch convert all .eml files in a directory to Markdown. Recursively finds .eml files (at most 50 per call; larger directories are rejected before any conversion). output_directory is required: Markdown is written there, mirroring subfolders, and source .eml files are left in place. Returns a JSON summary with total, successes, failures, output_paths, and errors. Each errors entry contains file and error_code (defaulting to conversion_error), never raw exception text. Use convert_eml to retrieve individual converted file content.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | – |
| dry_run | boolean | – | – |
| embed_inline_images | – | – | – |
| include_all_headers | – | – | – |
| include_raw_html | – | – | – |
| no_calendar_summary | – | – | – |
| output_directory | string | yes | – |
| preset | string | – | – |
| strip_disclaimers | – | – | – |
| strip_quoted_headers | – | – | – |
| strip_signature_images | – | – | – |
| strip_signatures | – | – | – |
| strip_tracking_pixels | – | – | – |
| thread_mode | string | – | – |
| thread_order | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
convert_eml Convert email ~295
Convert a .eml email file to Markdown with YAML front matter. Returns the full Markdown content (front matter + body). When output_path is provided, also writes the file to disk. Attachments are listed in the front matter but not written to disk; use convert_eml_to_bundle to save the decoded attachment files. thread_mode="structured" adds a section per earlier reply or forwarded message. Gmail HTML forwards and unquoted plain-text forwards are kept in latest mode too; a plain-text forward inside ">" quoting is not. Presets bundle common flag combinations: - default: strips signatures, tracking pixels, signature images - clean: default + strips disclaimers and quoted headers - verbose: includes all headers and raw HTML - raw: no stripping, preserves everything Individual flags override the preset when provided.
| Name | Type | Req | Description |
|---|---|---|---|
| embed_inline_images | – | – | – |
| eml_path | string | yes | – |
| include_all_headers | – | – | – |
| include_raw_html | – | – | – |
| no_calendar_summary | – | – | – |
| output_path | – | – | – |
| preset | string | – | – |
| strip_disclaimers | – | – | – |
| strip_quoted_headers | – | – | – |
| strip_signature_images | – | – | – |
| strip_signatures | – | – | – |
| strip_tracking_pixels | – | – | – |
| thread_mode | string | – | – |
| thread_order | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
convert_eml_to_bundle Convert email to bundle ~236
Convert a .eml file to a self-contained bundle with markdown and attachments. Creates a directory containing the converted markdown, extracted attachments, and optionally the original .eml source. source_handling only accepts 'copy' over MCP: the original .eml is copied into the bundle and left untouched. The 'move' and 'delete' modes are rejected here — use the CLI or the Python API for those. Returns JSON with bundle_path, markdown_path, attachment_paths, and optional diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_root | string | yes | – |
| embed_inline_images | – | – | – |
| eml_path | string | yes | – |
| include_all_headers | – | – | – |
| include_raw_html | – | – | – |
| no_calendar_summary | – | – | – |
| preset | string | – | – |
| source_handling | string | – | – |
| strip_disclaimers | – | – | – |
| strip_quoted_headers | – | – | – |
| strip_signature_images | – | – | – |
| strip_signatures | – | – | – |
| strip_tracking_pixels | – | – | – |
| thread_mode | string | – | – |
| thread_order | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
convert_mbox Convert MBOX archive ~293
Convert one flat .mbox archive (e.g. Gmail Takeout) to Markdown files. Bounded: the archive must be at most 256 MiB, and conversion stops after 1000 messages (the response then has truncated=true; use the dead-letter CLI for larger archives). Compressed archives and Apple Mail .mbox directories are rejected. output_directory is required; one .md per message (or one bundle directory when bundles=true) is written there with a collision-safe JSON report. The source archive is never modified. Returns a JSON summary (processed, converted, skipped, failed, truncated, report_path, and at most 20 failure entries), never message content. Cancellation is not supported; byte/message caps are not a time limit.
| Name | Type | Req | Description |
|---|---|---|---|
| bundles | boolean | – | – |
| dry_run | boolean | – | – |
| embed_inline_images | – | – | – |
| include_all_headers | – | – | – |
| include_raw_html | – | – | – |
| no_calendar_summary | – | – | – |
| output_directory | string | yes | – |
| path | string | yes | – |
| preset | string | – | – |
| strip_disclaimers | – | – | – |
| strip_quoted_headers | – | – | – |
| strip_signature_images | – | – | – |
| strip_signatures | – | – | – |
| strip_tracking_pixels | – | – | – |
| thread_mode | string | – | – |
| thread_order | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_diagnostics Get conversion diagnostics ~203
Inspect email quality and structure without writing permanent files. Use this to assess conversion quality before committing, or to troubleshoot problematic .eml files. Always returns JSON with: state (normal/degraded/review_recommended), selected_body, segmentation_path, client_hint, confidence, fallback_used, and warnings. Two keys are conditional: stripped_images appears only when images were removed, and attachments only when the message had attachments eligible for retention.
| Name | Type | Req | Description |
|---|---|---|---|
| embed_inline_images | – | – | – |
| eml_path | string | yes | – |
| include_all_headers | – | – | – |
| include_raw_html | – | – | – |
| no_calendar_summary | – | – | – |
| preset | string | – | – |
| strip_disclaimers | – | – | – |
| strip_quoted_headers | – | – | – |
| strip_signature_images | – | – | – |
| strip_signatures | – | – | – |
| strip_tracking_pixels | – | – | – |
| thread_mode | string | – | – |
| thread_order | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the dead-letter MCP server?
dead-letter runs locally as a container image, launched with docker run --rm -i ghcr.io/bigcactuslabs/dead-letter@sha256:08699fa81fd5be51b12cdbcbbcdd4333f8a2dd9d928d79ca1b9e34473beac8af. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. 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/bigcactuslabs/dead-letter
claude mcp add bigcactuslabs-dead-letter -- docker run --rm -i ghcr.io/bigcactuslabs/dead-letter@sha256:08699fa81fd5be51b12cdbcbbcdd4333f8a2dd9d928d79ca1b9e34473beac8af
The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.
What is the dead-letter MCP server?
dead-letter is an MCP server listed in the public MCP registry as io.github.BigCactusLabs/dead-letter. Convert .eml and .mbox email to clean Markdown for RAG, LLM pipelines, and local knowledge bases. This page covers its container image (ghcr.io/bigcactuslabs/dead-letter).
Is the dead-letter MCP server safe to use?
dead-letter scores 40 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 12 known advisories as of 5 November 2026. We do not grade that SBOM, as nothing verifies it. 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 dead-letter MCP server expose?
dead-letter exposes 5 tools: convert_eml, convert_eml_to_bundle, convert_directory, convert_mbox, get_diagnostics. Their descriptions and schemas cost roughly 1,267 tokens of context every time the server is loaded.
Is the dead-letter MCP server still maintained?
dead-letter is still listed as active in the MCP registry. We last reached this channel on 5 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 dead-letter MCP server under?
dead-letter declares the PolyForm-Noncommercial-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the dead-letter MCP server?
VerifyMCP ran 12 checks on dead-letter, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about dead-letter: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.