Wavyrai reMarkable MCP Server

MCP server for accessing reMarkable tablet data

MCP Servers Python Grade D Listed MIT
44.3/100
Rank #540 of 1283
Compare Wavyrai reMarkable MCP Server

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-04-12 · 122d ago
Recent change
Rank +1

Is Wavyrai reMarkable MCP Server safe? Wavyrai reMarkable MCP Server scores 44.3/100 (Grade D), ranked #540 of 1283 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; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-04-12. 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
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 21 spots (#518 → #539)
2026-08-08
Newly Listed
First tracked at rank #518
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 122 days ago. Fresh activity helps separate stable projects from stale ones.
19.6
Activity sub-score · out of 100
#195

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 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-08-12 05:02 UTC · Repo last pushed 122 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
17
Forks
6
Last Push
2026-04-12
122 days ago
Commits (4 wk)
0
Downloads (7d)
61
pypi
HN mentions (30d)
Open Issues
3
Rank Change
=
was #540

Analysis

HVTrust Dimensions vs MCP Servers

44.3 / 100 · 100.0% confidence

Wavyrai reMarkable MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
2.5 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
3.9 / 20
8.5 below avg 12.4
AdoptionLog-scaled stars · package downloads
5.4 / 20
in line with avg 5.8

Activity Inputs

19.6 / 100
StarsRepository reach
7.5 / 30
FreshnessLast push recency
8.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.9 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
Not available
Signed Commits
0%
of last 100 commits verified

Is Wavyrai reMarkable MCP Server safe?

Public trust evidence for Wavyrai reMarkable MCP Server 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 Wavyrai reMarkable MCP Server publish package provenance?
Yes. Wavyrai 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 Wavyrai reMarkable MCP Server have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Wavyrai reMarkable MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Wavyrai reMarkable MCP Server actively maintained?
Slowing down. Last push was 122 days ago — keep an eye on whether activity resumes.
What license does Wavyrai reMarkable MCP Server use?
Wavyrai reMarkable MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Wavyrai reMarkable MCP Server's commits signed?
0% of the last 100 commits to Wavyrai 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
Wavyrai 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 Wavyrai reMarkable MCP Server?

For maintainers

HVTrust scores Wavyrai 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
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 21 spots (#518 → #539)
2026-08-08
Newly Listed
First tracked at rank #518

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 44.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/wavyrai-remarkable-mcp-server.svg)](https://hvtracker.net/agents/wavyrai-remarkable-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/wavyrai-remarkable-mcp-server"><img src="https://hvtracker.net/badge/wavyrai-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON