updated 2026-11-11 00:08 UTC

reMarkable MCP Server

Repository

MCP server for accessing reMarkable tablet data - sync files, extract text from highlights, and browse your reMarkable cloud

MCP Servers Python Listed MIT

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

OSSF Scorecard 6.1 / 10
Provenance Attested
Signed commits 42%
Last push 6d ago
Advisories None known
Compare reMarkable MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: reMarkable MCP Server scores 71.0/100 (Grade B), ranked #350 of 1387 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 6.1/10; 42% of recent commits are signed; no published advisory affects its latest release (remarkable-mcp); last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How reMarkable MCP Server 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 reMarkable MCP Server 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 Partly signed

    github.com/SamMorrowDrums/remarkable-mcp, MIT, last pushed 2026-11-05. 42% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

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

  3. Published packages Partly attested

    • PyPI remarkable-mcp Source link isn't a GitHub repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: remarkable-mcp 2.1.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-28 OSSF Scorecard: 6.8/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 reMarkable MCP Server’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 reMarkable MCP Server compares in MCP Servers

  1. #204 Datawrapper 71.1 +0.1
  2. #205 Ros MCP Server 71.1 +0.1
  3. #206 reMarkable MCP Server 71.0 this agent
  4. #207 Cyberbro MCP Server 71.0 ±0
  5. #208 shadcn-ui MCP Server 71.0 ±0

Bars show each HVTrust score; the tick marks reMarkable MCP Server’s 71.0.

Where the 71.0 comes from

HVTrust dimensions vs the MCP Servers average

71.0 / 100 · 100.0% confidence

reMarkable MCP Server MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.2 / 25
6.4 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
1.4 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.6 / 20
0.7 below avg 12.3
AdoptionLog-scaled stars · package downloads
9.5 / 20
1.9 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-01
Rank Moved
Rank dropped 44 spots (#300 → #344)
2026-11-01
Activity Score Changed
Activity score down 10pts (57 → 47)
2026-10-24
Rank Moved
Rank rose 14 spots (#306 → #292)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/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.
Compare with another agent
View MCP Servers Report missing data
47.3
Activity sub-score · out of 100
#206
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-11-11 00:08 UTC · Repo last pushed 6 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
264
Forks
65
Last Push
2026-11-05
6 days ago
Commits (4 wk)
0
Downloads (7d)
583
pypi
HN mentions (30d)
—
Open Issues
14
Rank Change
=
was #350

Analysis

Activity Inputs

47.3 / 100
StarsRepository reach
14.5 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.5 / 20

Common questions about reMarkable MCP Server

reMarkable MCP Server 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 reMarkable MCP Server publish package provenance?
Yes. reMarkable MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does reMarkable MCP Server have an OpenSSF Scorecard?
reMarkable MCP Server has an OpenSSF Scorecard score of 6.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 reMarkable MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does reMarkable MCP Server use?
reMarkable MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are reMarkable MCP Server's commits signed?
42% of the last 100 commits to reMarkable MCP Server 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
medium confidence
Implemented
reMarkable MCP Server 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
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 reMarkable MCP Server'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 reMarkable MCP Server?

For maintainers

HVTrust scores reMarkable MCP Server 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 23Score 5Grade 5HVTrust 4Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-01
Rank Moved
Rank dropped 44 spots (#300 → #344)
2026-11-01
Activity Score Changed
Activity score down 10pts (57 → 47)
2026-10-24
Rank Moved
Rank rose 14 spots (#306 → #292)
2026-10-21
Rank Moved
Rank dropped 44 spots (#265 → #309)
2026-10-09
Rank Moved
Rank dropped 12 spots (#247 → #259)
2026-10-03
Rank Moved
Rank rose 16 spots (#260 → #244)
2026-10-02
Rank Moved
Rank rose 71 spots (#331 → #260)
2026-10-02
HVTrust Changed
HVTrust up 3.2pts (70.1 → 73.3)
2026-10-02
Activity Score Changed
Activity score up 14pts (44 → 58)
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 557 spots (#875 → #318)
2026-09-23
HVTrust Changed
HVTrust up 43.2pts (27.3 → 70.5)
2026-09-22
Newly Listed
First tracked at rank #875
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-14
Rank Moved
Rank dropped 41 spots (#250 → #291)
2026-09-14
Activity Score Changed
Activity score down 6pts (52 → 46)
2026-09-13
Rank Moved
Rank dropped 94 spots (#156 → #250)
2026-09-13
HVTrust Changed
HVTrust down 4.9pts (78.6 → 73.7)
2026-09-13
Activity Score Changed
Activity score down 16pts (68 → 52)
2026-09-12
Rank Moved
Rank dropped 22 spots (#134 → #156)
2026-09-10
Grade Changed
Trust grade A → B
2026-09-08
Grade Changed
Trust grade B → A
2026-09-08
Rank Moved
Rank rose 21 spots (#151 → #130)
2026-09-07
Rank Moved
Rank dropped 12 spots (#139 → #151)
2026-09-05
Rank Moved
Rank dropped 32 spots (#107 → #139)
2026-09-03
Grade Changed
Trust grade A → B
2026-09-03
Rank Moved
Rank dropped 26 spots (#77 → #103)
2026-08-31
Rank Moved
Rank dropped 13 spots (#71 → #84)
2026-08-28
Scorecard Added
OSSF Scorecard: 6.8/10
2026-08-28
Grade Changed
Trust grade B → A
2026-08-28
Rank Moved
Rank rose 135 spots (#208 → #73)
2026-08-28
HVTrust Changed
HVTrust up 14.1pts (67.8 → 81.9)
2026-08-27
Rank Moved
Rank dropped 11 spots (#197 → #208)
2026-08-26
Rank Moved
Rank dropped 13 spots (#184 → #197)
2026-08-24
Rank Moved
Rank dropped 13 spots (#170 → #183)
2026-08-19
Rank Moved
Rank dropped 14 spots (#160 → #174)
2026-08-17
Rank Moved
Rank rose 17 spots (#177 → #160)
2026-08-16
Rank Moved
Rank dropped 10 spots (#167 → #177)
2026-08-14
Rank Moved
Rank rose 56 spots (#224 → #168)
2026-08-14
Activity Score Changed
Activity score up 9pts (61 → 70)
GitHub → PyPI: remarkable-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 71.0 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/remarkable-mcp-server.svg)](https://hvtracker.net/agents/remarkable-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/remarkable-mcp-server"><img src="https://hvtracker.net/badge/remarkable-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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