Is Clipboard History MCP safe to use?

Clipboard History MCP has an HVTrust score of 39.6/100 (Grade D), ranked #1173 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Clipboard History MCP?

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

Clipboard History MCP

d-khomenko/clipboard-history-mcp

Type-aware, secret-safe clipboard history for Claude via MCP. Rust binary, macOS + Linux. Ships as .mcpb.

MCP Servers Rust Listed MIT

Is Clipboard History MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.6 / 10

Provenance None

Signed commits 26%

Last push 56d ago

Compare Clipboard History MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Clipboard History MCP scores 39.6/100 (Grade D), ranked #1173 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.6/10; 26% of recent commits are signed; last pushed 2026-08-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How Clipboard History MCP compares in MCP Servers

#694 MCP Server Code Runner 39.7 +0.1
#695 X64dbg MCP 39.7 +0.1
#696 Clipboard History MCP 39.6 this agent
#697 Pagecast 39.5 −0.1
#698 DataDoe MCP 39.5 −0.1

Bars show each HVTrust score; the tick marks Clipboard History MCP’s 39.6.

Where the 39.6 comes from

HVTrust dimensions vs the MCP Servers average

39.6 / 100 · 100.0% confidence

Clipboard History MCP MCP Servers average (775 agents)

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

5.8 / 25

4.5 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

8.3 / 20

3.8 below avg 12.1

AdoptionLog-scaled stars · package downloads

3.1 / 20

4.1 below avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Rank Moved

Rank dropped 423 spots (#746 → #1169)

2026-09-23

HVTrust Changed

HVTrust up 9.8pts (30.0 → 39.8)

2026-09-22

Newly Listed

First tracked at rank #746

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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 56 days ago. Fresh activity helps separate stable projects from stale ones.

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

25.2

Activity sub-score · out of 100

#696

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 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-01

56 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #1171

Analysis

Activity Inputs

25.2 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

17.2 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

0.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.6 / 10

OpenSSF Scorecard · scanned Sep 18, 2026

Signed Commits

26%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

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 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Clipboard History MCP

Public trust evidence for Clipboard History MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Clipboard History MCP publish package provenance?

No published build provenance is currently detected for Clipboard History MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Clipboard History MCP have an OpenSSF Scorecard?

Clipboard History MCP has an OpenSSF Scorecard score of 3.6/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 Clipboard History MCP actively maintained?

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

What license does Clipboard History MCP use?

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

Are Clipboard History MCP's commits signed?

26% of the last 100 commits to Clipboard History 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

None detected

No MCP server signal detected.

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

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Clipboard History MCP?

For maintainers

HVTrust scores Clipboard History 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

Rank Moved

Rank dropped 423 spots (#746 → #1169)

2026-09-23

HVTrust Changed

HVTrust up 9.8pts (30.0 → 39.8)

2026-09-22

Newly Listed

First tracked at rank #746

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 12 spots (#1134 → #1146)

2026-09-09

Rank Moved

Rank dropped 16 spots (#1114 → #1130)

2026-09-07

Rank Moved

Rank dropped 24 spots (#1084 → #1108)

2026-09-06

Rank Moved

Rank dropped 18 spots (#1066 → #1084)

2026-09-05

Rank Moved

Rank dropped 43 spots (#1023 → #1066)

2026-09-04

Rank Moved

Rank dropped 24 spots (#999 → #1023)

2026-09-03

Rank Moved

Rank dropped 56 spots (#943 → #999)

2026-09-02

Rank Moved

Rank dropped 50 spots (#893 → #943)

2026-09-01

Rank Moved

Rank dropped 35 spots (#858 → #893)

2026-08-31

Rank Moved

Rank dropped 46 spots (#812 → #858)

2026-08-30

Rank Moved

Rank dropped 29 spots (#783 → #812)

2026-08-29

Rank Moved

Rank dropped 48 spots (#735 → #783)

2026-08-28

Rank Moved

Rank dropped 28 spots (#707 → #735)

2026-08-27

Scorecard Added

OSSF Scorecard: 3.8/10

2026-08-27

Rank Moved

Rank rose 526 spots (#1233 → #707)

2026-08-27

HVTrust Changed

HVTrust up 25.2pts (17.3 → 42.5)

2026-08-26

Rank Moved

Rank dropped 34 spots (#1199 → #1233)

2026-08-16

Rank Moved

Rank dropped 24 spots (#1167 → #1191)

2026-08-10

Rank Moved

Rank dropped 66 spots (#1093 → #1159)

2026-08-08

Newly Listed

First tracked at rank #1091

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/clipboard-history-mcp.svg)](https://hvtracker.net/agents/clipboard-history-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/clipboard-history-mcp"><img src="https://hvtracker.net/badge/clipboard-history-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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