updated 2026-10-16 16:07 UTC

Cursor History MCP

Repository

MCP server for browsing, searching, and exporting Cursor AI chat history.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.9 / 10
Provenance Attested
Signed commits 100%
Last push 38d ago
Advisories None known
Compare Cursor History MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Cursor History MCP scores 68.8/100 (Grade B), ranked #386 of 1378 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.9/10; 100% of recent commits are signed; no published advisory affects its latest release (cursor-history-mcp); last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cursor History MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Cursor History MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/S2thend/cursor-history-mcp, MIT, last pushed 2026-09-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 4
    Packaging 10
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 1

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: cursor-history-mcp 0.3.1. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 3.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Cursor History MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Cursor History MCP compares in MCP Servers

  1. #228 Brave Search MCP Server 68.8 ±0
  2. #229 Edinet MCP 68.8 ±0
  3. #230 Cursor History MCP 68.8 this agent
  4. #231 Agrobr MCP 68.7 −0.1
  5. #232 Whoop MCP 68.6 −0.2

Bars show each HVTrust score; the tick marks Cursor History MCP’s 68.8.

Where the 68.8 comes from

HVTrust dimensions vs the MCP Servers average

68.8 / 100 · 100.0% confidence

Cursor History MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.4 / 25
6.9 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
9.5 / 20
2.8 below avg 12.3
AdoptionLog-scaled stars · package downloads
6.1 / 20
1.3 below avg 7.4

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-12
Rank Moved
Rank dropped 14 spots (#368 → #382)
2026-10-11
Rank Moved
Rank dropped 14 spots (#354 → #368)
2026-10-09
Rank Moved
Rank dropped 74 spots (#283 → #357)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.
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 Cursor History MCP View MCP Servers Report missing data
31.3
Activity sub-score · out of 100
#230
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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 38 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
33
Forks
2
Last Push
2026-09-08
38 days ago
Commits (4 wk)
0
Downloads (7d)
64
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲1
was #387

Analysis

Activity Inputs

31.3 / 100
StarsRepository reach
9.2 / 30
FreshnessLast push recency
19.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.2 / 20

Common questions about Cursor History MCP

Cursor History 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 Cursor History MCP publish package provenance?
Yes. Cursor History MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Cursor History MCP have an OpenSSF Scorecard?
Cursor History MCP has an OpenSSF Scorecard score of 3.9/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 Cursor History MCP actively maintained?
Slowing down. Last push was 38 days ago — keep an eye on whether activity resumes.
What license does Cursor History MCP use?
Cursor History MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cursor History MCP's commits signed?
100% of the last 100 commits to Cursor 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
high confidence
Implemented
Cursor History 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 Cursor History 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-09-08
Activity Resumed
Activity resumed

Maintain Cursor History MCP?

For maintainers

HVTrust scores Cursor 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
Rank 24HVTrust 5Grade 3Listed 2Score 2Scorecard 1Fresh 1Delisted 1Provenance 1MCP 1
2026-10-12
Rank Moved
Rank dropped 14 spots (#368 → #382)
2026-10-11
Rank Moved
Rank dropped 14 spots (#354 → #368)
2026-10-09
Rank Moved
Rank dropped 74 spots (#283 → #357)
2026-10-09
HVTrust Changed
HVTrust down 3.0pts (72.6 → 69.6)
2026-10-09
Activity Score Changed
Activity score down 9pts (41 → 32)
2026-10-03
Rank Moved
Rank dropped 27 spots (#250 → #277)
2026-09-27
Rank Moved
Rank rose 43 spots (#282 → #239)
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 762 spots (#1044 → #282)
2026-09-23
HVTrust Changed
HVTrust up 48.5pts (23.9 → 72.4)
2026-09-22
Newly Listed
First tracked at rank #1044
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 43 spots (#309 → #266)
2026-09-09
Rank Moved
Rank dropped 32 spots (#244 → #276)
2026-09-08
Activity Resumed
Activity resumed
2026-09-08
Grade Changed
Trust grade C → B
2026-09-08
Rank Moved
Rank rose 375 spots (#619 → #244)
2026-09-08
HVTrust Changed
HVTrust up 14.8pts (58.6 → 73.4)
2026-09-08
Activity Score Changed
Activity score up 34pts (11 → 45)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 499 spots (#1118 → #619)
2026-09-07
HVTrust Changed
HVTrust up 19.1pts (39.5 → 58.6)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1104 → #1118)
2026-09-05
Rank Moved
Rank dropped 39 spots (#1065 → #1104)
2026-09-04
Rank Moved
Rank dropped 24 spots (#1041 → #1065)
2026-09-03
Rank Moved
Rank dropped 57 spots (#984 → #1041)
2026-09-02
Rank Moved
Rank dropped 48 spots (#936 → #984)
2026-09-01
Rank Moved
Rank dropped 38 spots (#898 → #936)
2026-08-31
Rank Moved
Rank dropped 30 spots (#868 → #898)
2026-08-30
Rank Moved
Rank dropped 33 spots (#835 → #868)
2026-08-29
Rank Moved
Rank dropped 46 spots (#789 → #835)
2026-08-28
Rank Moved
Rank dropped 24 spots (#765 → #789)
2026-08-27
Rank Moved
Rank dropped 24 spots (#741 → #765)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-26
Rank Moved
Rank dropped 25 spots (#716 → #741)
2026-08-26
HVTrust Changed
HVTrust up 4.8pts (34.9 → 39.7)
2026-08-16
Rank Moved
Rank dropped 13 spots (#696 → #709)
2026-08-10
Rank Moved
Rank dropped 32 spots (#662 → #694)
2026-08-08
Newly Listed
First tracked at rank #662
GitHub → npm: cursor-history-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 68.8 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/cursor-history-mcp.svg)](https://hvtracker.net/agents/cursor-history-mcp)
HTML:
<a href="https://hvtracker.net/agents/cursor-history-mcp"><img src="https://hvtracker.net/badge/cursor-history-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.4 · Raw JSON