reMarkable MCP Server

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

MCP Servers Python Grade B Listed MIT
79.0/100
Rank #107 of 1320
Compare reMarkable MCP Server

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-17 · 18d ago
Recent change
Grade Changed +6

Is reMarkable MCP Server safe? reMarkable MCP Server scores 79.0/100 (Grade B), ranked #107 of 1320 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.8/10; 43% of recent commits are signed; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.8/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.
68.3
Activity sub-score · out of 100
#47

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-09-04 23:32 UTC · Repo last pushed 18 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
218
Forks
48
Last Push
2026-08-17
18 days ago
Commits (4 wk)
82
Downloads (7d)
420
pypi
HN mentions (30d)
Open Issues
7
Rank Change
▼4
was #103

Analysis

HVTrust Dimensions vs MCP Servers

79.0 / 100 · 100.0% confidence

reMarkable MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.1 / 25
8.5 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.3 / 17
2.5 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
18.5 / 20
6.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.1 / 20
2.8 above avg 6.3

Activity Inputs

68.3 / 100
StarsRepository reach
14.0 / 30
FreshnessLast push recency
22.5 / 25
ActivityRecent commits
23.9 / 25
CommunityFork signal
7.9 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
6.8 / 10
OpenSSF Scorecard · scanned Aug 29, 2026
Signed Commits
43%
of last 100 commits verified
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 9

Is reMarkable MCP Server safe?

Public supply-chain signals for reMarkable MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but reMarkable MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
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.8/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?
Maintained. Last push was 18 days ago.
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?
43% 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

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.

Reputation Timeline

Signal history
Rank 13Grade 3Score 2HVTrust 2Listed 1Scorecard 1
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)
2026-08-13
Grade Changed
Trust grade C → B
2026-08-13
Rank Moved
Rank rose 131 spots (#355 → #224)
2026-08-13
HVTrust Changed
HVTrust up 7.5pts (57.8 → 65.3)
2026-08-13
Activity Score Changed
Activity score up 20pts (40 → 61)
2026-08-12
Rank Moved
Rank rose 14 spots (#369 → #355)
2026-08-10
Rank Moved
Rank dropped 20 spots (#349 → #369)
2026-08-08
Newly Listed
First tracked at rank #351

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 79.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.3 · Raw JSON