Is E18e MCP safe to use?

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

What is the trust score for E18e MCP?

E18e MCP scores 67.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 19 GitHub stars and is categorized under MCP Servers.

E18e MCP

e18e/mcp

The official e18e MCP server

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 4.5 / 10

Provenance Attested

Signed commits 44%

Last push 38d ago

Compare E18e MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: E18e MCP scores 67.0/100 (Grade B), ranked #404 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.5/10; 44% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How E18e MCP compares in MCP Servers

#239 Azure DevOps (ADO) 67.0 ±0
#240 MCP Server for WinDbg Crash Analysis 67.0 ±0
#241 E18e MCP 67.0 this agent
#242 Brilliant Directories MCP 67.0 ±0
#243 Docspace MCP 67.0 ±0

Bars show each HVTrust score; the tick marks E18e MCP’s 67.0.

Where the 67.0 comes from

HVTrust dimensions vs the MCP Servers average

67.0 / 100 · 100.0% confidence

E18e MCP MCP Servers average (775 agents)

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

15.3 / 25

5.0 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.3 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.5 / 20

2.6 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.9 / 20

1.3 below 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.5/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 38 days ago. Fresh activity helps separate stable projects from stale ones.

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

29.9

Activity sub-score · out of 100

#241

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

Forks

Last Push

2026-08-19

38 days ago

Commits (4 wk)

Downloads (7d)

131

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #406

Analysis

Activity Inputs

29.9 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

19.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

44%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 8

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about E18e MCP

E18e 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 E18e MCP publish package provenance?

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

Does E18e MCP have an OpenSSF Scorecard?

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

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

What license does E18e MCP use?

E18e MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are E18e MCP's commits signed?

43% of the last 100 commits to E18e 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

E18e 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 E18e 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

Maintain E18e MCP?

For maintainers

HVTrust scores E18e 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 713 spots (#1104 → #391)

2026-09-23

HVTrust Changed

HVTrust up 45.2pts (22.0 → 67.2)

2026-09-22

Newly Listed

First tracked at rank #1104

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 29 spots (#354 → #383)

2026-09-12

Grade Changed

Trust grade D → B

2026-09-12

Rank Moved

Rank rose 681 spots (#1016 → #335)

2026-09-12

HVTrust Changed

HVTrust up 22.8pts (46.3 → 69.1)

2026-09-11

Rank Moved

Rank dropped 10 spots (#1006 → #1016)

2026-09-09

Rank Moved

Rank dropped 16 spots (#993 → #1009)

2026-09-07

Rank Moved

Rank dropped 70 spots (#914 → #984)

2026-09-07

Activity Score Changed

Activity score down 6pts (42 → 36)

2026-09-06

Rank Moved

Rank dropped 14 spots (#900 → #914)

2026-09-05

Rank Moved

Rank dropped 55 spots (#845 → #900)

2026-09-04

Rank Moved

Rank dropped 37 spots (#808 → #845)

2026-09-03

Rank Moved

Rank dropped 47 spots (#761 → #808)

2026-09-02

Rank Moved

Rank dropped 35 spots (#726 → #761)

2026-09-01

Rank Moved

Rank dropped 31 spots (#695 → #726)

2026-08-31

Rank Moved

Rank dropped 34 spots (#661 → #695)

2026-08-30

Rank Moved

Rank dropped 24 spots (#637 → #661)

2026-08-29

Scorecard Added

OSSF Scorecard: 4.5/10

2026-08-29

Rank Moved

Rank rose 103 spots (#740 → #637)

2026-08-29

HVTrust Changed

HVTrust up 6.2pts (42.1 → 48.3)

2026-08-28

Rank Moved

Rank dropped 26 spots (#714 → #740)

2026-08-27

Rank Moved

Rank dropped 21 spots (#693 → #714)

2026-08-26

Rank Moved

Rank dropped 98 spots (#595 → #693)

2026-08-16

Rank Moved

Rank dropped 11 spots (#583 → #594)

2026-08-10

Rank Moved

Rank dropped 21 spots (#551 → #572)

2026-08-08

Newly Listed

First tracked at rank #549

GitHub → npm: @e18e/mcp

Embed Badge Badge guide for maintainers →

For maintainers

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