Is Better Email MCP safe to use?

Better Email MCP has an HVTrust score of 84.9/100 (Grade A), ranked #57 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Better Email MCP?

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

Better Email MCP

n24q02m/better-email-mcp

IMAP/SMTP email for AI agents -- read, send, organize folders, and manage attachments across multiple accounts, with aut

MCP Servers TypeScript Grade A Listed Apache-2.0

84.9/100

Rank #57 of 1320

Compare Better Email MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-02 · 2d ago

Recent change

Grade Changed +7

Is Better Email MCP safe? Better Email MCP scores 84.9/100 (Grade A), ranked #57 of 1320 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 7.1/10; 74% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#14 Containers Kubernetes MCP Server — 86.1 (A) → #15 KiCad MCP Pro — 85.6 (A) → #17 Stripe Agent Toolkit — 84.5 (A) → #18 Browserstack MCP Server — 83.6 (A) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-04

Grade Changed

Trust grade C → A

2026-09-04

Rank Moved

Rank rose 510 spots (#567 → #57)

2026-09-04

HVTrust Changed

HVTrust up 28.9pts (56.0 → 84.9)

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

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

62.5

Activity sub-score · out of 100

#16

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 →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-02

2 days ago

Commits (4 wk)

Downloads (7d)

688

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲510

was #567

Analysis

HVTrust Dimensions vs MCP Servers

84.9 / 100 · 100.0% confidence

Better Email MCP MCP Servers average (778 agents)

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

20.1 / 25

10.6 above avg 9.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

2.7 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

19.1 / 20

6.9 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.5 / 20

1.3 above avg 6.2

Activity Inputs

62.5 / 100

StarsRepository reach

9.3 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

22.7 / 25

CommunityFork signal

5.6 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.1 / 10

OpenSSF Scorecard · scanned Aug 30, 2026

Signed Commits

74%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Is Better Email MCP safe?

Public supply-chain signals for Better Email MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Better Email MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Better Email MCP publish package provenance?

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

Does Better Email MCP have an OpenSSF Scorecard?

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

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does Better Email MCP use?

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

Are Better Email MCP's commits signed?

74% of the last 100 commits to Better 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

Better Email MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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

Maintain Better Email MCP?

For maintainers

HVTrust scores Better 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-04

Grade Changed

Trust grade C → A

2026-09-04

Rank Moved

Rank rose 510 spots (#567 → #57)

2026-09-04

HVTrust Changed

HVTrust up 28.9pts (56.0 → 84.9)

2026-09-03

Rank Moved

Rank dropped 41 spots (#526 → #567)

2026-09-02

Rank Moved

Rank dropped 11 spots (#515 → #526)

2026-08-31

Rank Moved

Rank dropped 30 spots (#478 → #508)

2026-08-30

Rank Moved

Rank rose 17 spots (#495 → #478)

2026-08-29

Rank Moved

Rank dropped 23 spots (#472 → #495)

2026-08-27

Rank Moved

Rank dropped 13 spots (#455 → #468)

2026-08-26

Scorecard Added

OSSF Scorecard: 7.0/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 66 spots (#521 → #455)

2026-08-26

HVTrust Changed

HVTrust up 9.8pts (45.9 → 55.7)

2026-08-24

Rank Moved

Rank dropped 18 spots (#505 → #523)

2026-08-22

Rank Moved

Rank rose 12 spots (#520 → #508)

2026-08-13

Rank Moved

Rank dropped 10 spots (#499 → #509)

2026-08-10

Rank Moved

Rank dropped 17 spots (#489 → #506)

2026-08-08

Newly Listed

First tracked at rank #486

GitHub → npm: @n24q02m/better-email-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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