updated 2026-10-16 16:07 UTC

Imap MCP Server

Repository

Full-featured IMAP & SMTP email for AI assistants: search, read, send, organize and clean up multiple mailboxes, with AES-256-encrypted credentials. Works with Claude, Cursor and any MCP client.

MCP Servers TypeScript Listed MIT

Is Imap MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.0 / 10
Provenance Attested
Signed commits 66%
Last push 2d ago
Advisories None known
Compare Imap MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Imap MCP Server scores 81.5/100 (Grade A), ranked #138 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 66% of recent commits are signed; no published advisory affects its latest release (imap-mcp-server); last pushed 2026-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Imap MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Imap MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/nikolausm/imap-mcp-server, MIT, last pushed 2026-10-14. 66% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.0/10 (scanned Oct 12, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 4
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

    • npm imap-mcp-server Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: imap-mcp-server 2.2.0. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 6.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Imap MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Imap MCP Server compares in MCP Servers

  1. #58 UniFi Access MCP 81.8 +0.3
  2. #59 Zotero MCP 81.6 +0.1
  3. #60 Imap MCP Server 81.5 this agent
  4. #61 Filesystem MCP 81.4 −0.1
  5. #62 Claude Prompts MCP 81.4 −0.1

Bars show each HVTrust score; the tick marks Imap MCP Server’s 81.5.

Where the 81.5 comes from

HVTrust dimensions vs the MCP Servers average

81.5 / 100 · 100.0% confidence

Imap MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.3 / 25
7.8 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.6 / 17
1.3 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.1 / 20
4.8 above avg 12.3
AdoptionLog-scaled stars · package downloads
9.5 / 20
2.1 above avg 7.4

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-14
Rank Moved
Rank dropped 11 spots (#128 → #139)
2026-10-11
Rank Moved
Rank rose 16 spots (#152 → #136)
2026-10-10
Rank Moved
Rank dropped 24 spots (#128 → #152)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent Get email alerts for Imap MCP Server View MCP Servers Report missing data
61.9
Activity sub-score · out of 100
#60
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
111
Forks
57
Last Push
2026-10-14
2 days ago
Commits (4 wk)
20
Downloads (7d)
2,664
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
▼1
was #137

Analysis

Activity Inputs

61.9 / 100
StarsRepository reach
12.3 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
16.5 / 25
CommunityFork signal
8.2 / 20

Common questions about Imap MCP Server

Public supply-chain signals for Imap MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Imap MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Imap MCP Server publish package provenance?
Yes. Imap MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Imap MCP Server have an OpenSSF Scorecard?
Imap MCP Server has an OpenSSF Scorecard score of 6.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Imap MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Imap MCP Server use?
Imap MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Imap MCP Server's commits signed?
66% of the last 100 commits to Imap MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Imap MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Imap MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Imap MCP Server?

For maintainers

HVTrust scores Imap MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 26Grade 4HVTrust 3Listed 2Scorecard 1Score 1Delisted 1Provenance 1MCP 1
2026-10-14
Rank Moved
Rank dropped 11 spots (#128 → #139)
2026-10-11
Rank Moved
Rank rose 16 spots (#152 → #136)
2026-10-10
Rank Moved
Rank dropped 24 spots (#128 → #152)
2026-09-26
Rank Moved
Rank rose 11 spots (#133 → #122)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 591 spots (#722 → #131)
2026-09-23
HVTrust Changed
HVTrust up 50.9pts (30.4 → 81.3)
2026-09-22
Newly Listed
First tracked at rank #722
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 18 spots (#139 → #121)
2026-09-19
Activity Score Changed
Activity score up 6pts (57 → 63)
2026-09-16
Grade Changed
Trust grade B → A
2026-09-16
Rank Moved
Rank rose 31 spots (#166 → #135)
2026-09-07
Grade Changed
Trust grade C → B
2026-09-07
Rank Moved
Rank rose 642 spots (#802 → #160)
2026-09-07
HVTrust Changed
HVTrust up 26.5pts (51.6 → 78.1)
2026-09-06
Rank Moved
Rank dropped 10 spots (#792 → #802)
2026-09-05
Rank Moved
Rank dropped 96 spots (#696 → #792)
2026-09-04
Rank Moved
Rank dropped 43 spots (#653 → #696)
2026-09-03
Rank Moved
Rank dropped 41 spots (#612 → #653)
2026-09-02
Rank Moved
Rank dropped 24 spots (#588 → #612)
2026-09-01
Rank Moved
Rank dropped 17 spots (#571 → #588)
2026-08-31
Rank Moved
Rank dropped 23 spots (#548 → #571)
2026-08-29
Rank Moved
Rank dropped 29 spots (#519 → #548)
2026-08-27
Rank Moved
Rank dropped 12 spots (#500 → #512)
2026-08-26
Scorecard Added
OSSF Scorecard: 6.1/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 34 spots (#534 → #500)
2026-08-26
HVTrust Changed
HVTrust up 8.5pts (44.9 → 53.4)
2026-08-24
Rank Moved
Rank dropped 15 spots (#521 → #536)
2026-08-22
Rank Moved
Rank rose 12 spots (#534 → #522)
2026-08-21
Rank Moved
Rank rose 12 spots (#546 → #534)
2026-08-19
Rank Moved
Rank dropped 10 spots (#530 → #540)
2026-08-17
Rank Moved
Rank rose 10 spots (#541 → #531)
2026-08-13
Rank Moved
Rank dropped 16 spots (#507 → #523)
2026-08-12
Rank Moved
Rank rose 11 spots (#518 → #507)
2026-08-10
Rank Moved
Rank dropped 12 spots (#503 → #515)
2026-08-08
Newly Listed
First tracked at rank #499
GitHub → npm: imap-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 81.5 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/imap-mcp-server.svg)](https://hvtracker.net/agents/imap-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/imap-mcp-server"><img src="https://hvtracker.net/badge/imap-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON