Is MCP Me safe to use?

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

What is the trust score for MCP Me?

MCP Me scores 61.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 18 GitHub stars and is categorized under MCP Servers.

MCP Me

paladini/mcp-me

Your AI assistants don't know who you are. mcp-me fixes that: a local MCP server that gives any AI a full picture of who you are

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.5 / 10

Provenance Attested

Signed commits 18%

Last push 46d ago

Compare MCP Me

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Me scores 61.4/100 (Grade C), ranked #596 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 3.5/10; 18% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Me compares in MCP Servers

#333 Unreal Engine API Documentation 61.6 +0.2
#334 Web Researcher MCP 61.5 +0.1
#335 MCP Me 61.4 this agent
#336 Desktop Commander MCP 61.3 −0.1
#337 Replicant MCP 61.3 −0.1

Bars show each HVTrust score; the tick marks MCP Me’s 61.4.

Where the 61.4 comes from

HVTrust dimensions vs the MCP Servers average

61.4 / 100 · 100.0% confidence

MCP Me MCP Servers average (775 agents)

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

12.8 / 25

2.5 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

11.5 / 17

0.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

8.9 / 20

3.2 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.5 / 20

1.7 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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.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 46 days ago. Fresh activity helps separate stable projects from stale ones.

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

29.8

Activity sub-score · out of 100

#335

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 C 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-11

46 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #593

Analysis

Activity Inputs

29.8 / 100

StarsRepository reach

7.7 / 30

FreshnessLast push recency

18.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.3 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

3.5 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

18%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 6

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Me

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

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

Does MCP Me have an OpenSSF Scorecard?

MCP Me has an OpenSSF Scorecard score of 3.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 MCP Me actively maintained?

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

What license does MCP Me use?

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

Are MCP Me's commits signed?

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

MCP Me 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

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

How this surface has changed

Detected changes to MCP Me'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain MCP Me?

For maintainers

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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

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

2026-09-23

Rank Moved

Rank rose 578 spots (#1164 → #586)

2026-09-23

HVTrust Changed

HVTrust up 41.3pts (20.3 → 61.6)

2026-09-22

Newly Listed

First tracked at rank #1164

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 11 spots (#531 → #542)

2026-09-10

Rank Moved

Rank dropped 44 spots (#487 → #531)

2026-09-08

Rank Moved

Rank dropped 12 spots (#472 → #484)

2026-09-07

Rank Moved

Rank dropped 44 spots (#428 → #472)

2026-09-06

Rank Moved

Rank dropped 13 spots (#415 → #428)

2026-09-05

Rank Moved

Rank dropped 69 spots (#346 → #415)

2026-09-04

Rank Moved

Rank dropped 13 spots (#333 → #346)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 578 spots (#911 → #333)

2026-09-03

HVTrust Changed

HVTrust up 21.7pts (42.7 → 64.4)

2026-09-02

Rank Moved

Rank dropped 52 spots (#859 → #911)

2026-09-01

Rank Moved

Rank dropped 30 spots (#829 → #859)

2026-08-31

Rank Moved

Rank dropped 31 spots (#798 → #829)

2026-08-30

Rank Moved

Rank dropped 28 spots (#770 → #798)

2026-08-29

Rank Moved

Rank dropped 48 spots (#722 → #770)

2026-08-28

Rank Moved

Rank dropped 25 spots (#697 → #722)

2026-08-27

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-27

Rank Moved

Rank rose 73 spots (#770 → #697)

2026-08-27

HVTrust Changed

HVTrust up 4.8pts (38.2 → 43.0)

2026-08-26

Rank Moved

Rank dropped 105 spots (#665 → #770)

2026-08-22

Rank Moved

Rank dropped 34 spots (#624 → #658)

2026-08-22

Activity Score Changed

Activity score down 8pts (48 → 40)

2026-08-16

Rank Moved

Rank dropped 13 spots (#609 → #622)

2026-08-10

Rank Moved

Rank dropped 30 spots (#591 → #621)

2026-08-08

Newly Listed

First tracked at rank #588

GitHub → npm: mcp-me

Embed Badge Badge guide for maintainers →

For maintainers

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