Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

rubit-mcp-mail

PYPI · RUBIT-MCP-MAIL

Read-only MCP server for your mail — provider-agnostic IMAP that never marks a message as read.

Available components

+15 this week 97 Trust /100

Last scanned (8 hours ago)

Scores higher than 99% of PyPI servers

Category Communication

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 50 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to bgalmes/rubit-mcp-mail). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 49 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 664 tokens (~110/item across 6 items; 6 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
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 30 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 25 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 24 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 23 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
Diagnostics

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 pypi/rubit-mcp-mail@1.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo bgalmes/rubit-mcp-mail
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/bgalmes/rubit-mcp-mail/.github/workflows/publish-release.yml@refs/heads/main
Rekor log index 2863916057
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:1e842b57ac9ddc90116b22da508259eaacce5711a0cb15e306fd3b195cf016e2

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 50 packages
Packages resolved 50
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~581 tokens

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 →

Tool Tokens
get_attachment ~90

Download one attachment into the configured download directory. Returns the path it was saved to. Files are only ever written inside that one directory; the mailbox itself is not modified.

NameTypeReqDescription
account––Account name. Optional when only one is configured.
handlestringyesA handle from list_messages or search_messages.
part_idstringyesThe `part_id` from read_message's attachments.
NameTypeReqDescription
result–yes–

No examples provided.

list_accounts ~29

List configured mail accounts and whether each is authenticated. Call this first if another tool reports an authentication problem.

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yes–

No examples provided.

list_folders ~69

List the folders in a mailbox with message and unread counts. Each folder has a normalized `role` that is stable across providers, so you can ask for 'junk' without knowing the server calls it 'Junk Email'.

NameTypeReqDescription
account––Account name. Optional when only one is configured.
NameTypeReqDescription
result–yes–

No examples provided.

list_messages ~124

Browse messages in a folder, newest first. Returns summaries only (no bodies). Pass a returned `handle` to read_message to get the full text.

NameTypeReqDescription
account––Account name. Optional when only one is configured.
folderstring–Folder role ('inbox', 'sent', 'junk', 'trash', 'drafts', 'archive') or a raw server folder name.
limitinteger–Max messages to return.
offsetinteger–Messages to skip, for paging.
unread_onlyboolean–Only unread mail.
NameTypeReqDescription
result–yes–

No examples provided.

read_message ~85

Read one message in full: headers, body text, and attachment metadata. HTML-only mail is converted to text. This does NOT mark the message as read.

NameTypeReqDescription
account––Account name. Optional when only one is configured.
handlestringyesA handle from list_messages or search_messages.
max_charsinteger–Truncate the body beyond this many characters.
NameTypeReqDescription
result–yes–

No examples provided.

search_messages ~184

Search a folder. All supplied criteria are combined with AND. Server-side IMAP search, so it works over the whole folder without downloading anything. Results are newest first.

NameTypeReqDescription
account––Account name. Optional when only one is configured.
before––Strictly before this date.
folderstring–Folder role ('inbox', 'sent', 'junk', 'trash', 'drafts', 'archive') or a raw server folder name.
from_––Substring of the sender address or name.
limitinteger–Max messages to return.
offsetinteger–Messages to skip, for paging.
since––On or after this date.
subject––Substring of the subject.
text––Free text, matched against headers and body.
unread_onlyboolean–Only unread mail.
NameTypeReqDescription
result–yes–

No examples provided.

Install

How do I install the rubit-mcp-mail server?

rubit-mcp-mail runs locally as a PyPI package, launched with uvx rubit-mcp-mail serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · rubit-mcp-mail

# add to Claude Code
claude mcp add bgalmes-rubit-mcp-mail -- uvx rubit-mcp-mail serve
Common questions

What is the rubit-mcp-mail server?

rubit-mcp-mail is listed in the public MCP registry as io.github.bgalmes/rubit-mcp-mail. Read-only MCP server for your mail, provider-agnostic IMAP that never marks a message as read. This page covers its PyPI package (rubit-mcp-mail).

Is the rubit-mcp-mail server safe to use?

rubit-mcp-mail scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 rubit-mcp-mail server expose?

rubit-mcp-mail exposes 6 tools: list_accounts, list_folders, list_messages, search_messages, read_message, get_attachment. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.

Is the rubit-mcp-mail server still maintained?

rubit-mcp-mail 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 rubit-mcp-mail server under?

rubit-mcp-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.

What did VerifyMCP test on the rubit-mcp-mail server?

VerifyMCP ran 16 checks on rubit-mcp-mail, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.