Is Email MCP safe to use?

Email MCP has an HVTrust score of 68.0/100 (Grade B), ranked #375 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Email MCP?

Email MCP scores 68.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 117 GitHub stars and is categorized under MCP Servers.

Email MCP

codefuturist/email-mcp

Email MCP server with full IMAP + SMTP support — read, search, send, manage, and organize email from any AI assistant via the Model Context Protocol

MCP Servers TypeScript Listed LGPL-3.0

Is Email MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.3 / 10

Provenance Attested

Signed commits 6%

Last push 36d ago

Compare Email MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Email MCP scores 68.0/100 (Grade B), ranked #375 of 1325 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 4.3/10; 6% of recent commits are signed; last pushed 2026-08-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Email MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Email MCP’s 68.0.

Where the 68.0 comes from

HVTrust dimensions vs the MCP Servers average

68.0 / 100 · 100.0% confidence

Email MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.2 / 25

2.9 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.6 / 20

2.5 below avg 12.1

AdoptionLog-scaled stars · package downloads

9.0 / 20

1.8 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

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 → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 36 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Email MCP View MCP Servers Report missing data

40.7

Activity sub-score · out of 100

#227

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 B 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

117

Forks

Last Push

2026-08-21

36 days ago

Commits (4 wk)

Downloads (7d)

978

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #377

Analysis

Activity Inputs

40.7 / 100

StarsRepository reach

12.4 / 30

FreshnessLast push recency

20.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.2 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Email MCP

Email MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Email MCP publish package provenance?

Yes. Email MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Email MCP have an OpenSSF Scorecard?

Email MCP has an OpenSSF Scorecard score of 4.3/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 Email MCP actively maintained?

Slowing down. Last push was 36 days ago — keep an eye on whether activity resumes.

What license does Email MCP use?

Email MCP ships under LGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Email MCP's commits signed?

6% of the last 100 commits to Email MCP 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

Email MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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 Email MCP'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

2026-08-21

Activity Resumed

Activity resumed

2026-08-18

Activity Went Stale

No commits for 90 days

Maintain Email MCP?

For maintainers

HVTrust scores Email MCP 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

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 → B

2026-09-23

Rank Moved

Rank rose 687 spots (#1062 → #375)

2026-09-23

HVTrust Changed

HVTrust up 45.0pts (23.1 → 68.1)

2026-09-22

Newly Listed

First tracked at rank #1062

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 10 spots (#330 → #340)

2026-09-07

Rank Moved

Rank dropped 38 spots (#282 → #320)

2026-09-05

Rank Moved

Rank dropped 58 spots (#220 → #278)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.3/10

2026-09-02

Grade Changed

Trust grade D → B

2026-09-02

Rank Moved

Rank rose 731 spots (#938 → #207)

2026-09-02

HVTrust Changed

HVTrust up 30.8pts (39.6 → 70.4)

2026-09-01

Rank Moved

Rank dropped 35 spots (#903 → #938)

2026-08-31

Rank Moved

Rank dropped 33 spots (#870 → #903)

2026-08-30

Rank Moved

Rank dropped 38 spots (#832 → #870)

2026-08-29

Rank Moved

Rank dropped 39 spots (#793 → #832)

2026-08-28

Rank Moved

Rank dropped 31 spots (#762 → #793)

2026-08-27

Rank Moved

Rank dropped 27 spots (#735 → #762)

2026-08-26

Rank Moved

Rank dropped 96 spots (#639 → #735)

2026-08-21

Activity Resumed

Activity resumed

2026-08-21

Rank Moved

Rank rose 68 spots (#703 → #635)

2026-08-21

HVTrust Changed

HVTrust up 4.1pts (36.0 → 40.1)

2026-08-21

Activity Score Changed

Activity score up 13pts (32 → 45)

2026-08-18

Activity Went Stale

No commits for 90 days

2026-08-16

Rank Moved

Rank dropped 13 spots (#682 → #695)

2026-08-10

Rank Moved

Rank dropped 30 spots (#651 → #681)

2026-08-08

Newly Listed

First tracked at rank #649

GitHub → npm: @codefuturist/email-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/email-mcp.svg)](https://hvtracker.net/agents/email-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/email-mcp"><img src="https://hvtracker.net/badge/email-mcp.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.3 · Raw JSON