reMarkable MCP Server (SamMorrowDrums/remarkable-mcp) is an MCP server listed on the M8ven Trust Index. It scores 36 out of 100, grade F. It declares 15 tools. No publisher has claimed this listing.

Warning

36/100

reMarkable MCP Server

Item: reMarkable MCP Server
Rating: 36
Author: M8ven

Enables AI assistants to read, search, and traverse your entire reMarkable library, including handwritten notes via OCR.

→ SamMorrowDrums/remarkable-mcp · listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

SamMorrowDrums

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

⚠️

Tool descriptions don’t match what handlers do

3 tools describe read intent but their handlers mutate — remarkable_read (line 400: tmp_path.unlink(missing_ok=True)); remarkable_recent (line 1128: tmp_path.unlink(missing_ok=True)); remarkable_image (line 1822: ocr_tmp_path.unlink(missing_ok=True))

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 4 credentials: REMARKABLE_TOKEN, REMARKABLE_SSH_KEY, GOOGLE_VISION_API_KEY, REMARKABLE_SSH_PASSWORD

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// tools this server exposes14 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

remarkable_canvas

<usecase>Open a reMarkable page in an interactive canvas viewer.</usecase> <instructions> Renders a notebook or document page and, in clients that support MCP Apps interactive UI, opens a canvas viewer that lets the user page through the document. This is the entry point for the interactive viewer.

my_tool

my_ocr_tool

remarkable_read

<usecase>Read and extract text content from a reMarkable document.</usecase> <instructions> Extracts content from a document with pagination to preserve context window.

remarkable_browse

<usecase>Browse your reMarkable library or search for documents.</usecase> <instructions> Three modes: 1. Browse mode (default): List contents of a folder - Use path="/" for root folder - Use path="/FolderName" to navigate into folders 2. Search mode: Find documents by name - Set query="search term"…

remarkable_recent

<usecase>Get your most recently modified documents.</usecase> <instructions> Returns documents sorted by modification date (newest first). Optionally includes a text preview of each document's content.

remarkable_search

<usecase>Search across multiple documents and return matching content.</usecase> <instructions> Searches document names for the query, then optionally searches content with grep. Can filter by tags to narrow results. Returns summaries from multiple documents in a single call.

remarkable_status

<usecase>Check connection status, active transport, and write capabilities.</usecase> <instructions> Returns authentication status, the active transport (cloud, ssh, or usb-web), the document count, and a capability matrix describing what each transport can do. Use this to verify your connection, ch…

remarkable_image

<usecase>Get an image of a specific page from a reMarkable document.</usecase> <instructions> Renders a notebook or document page as an image (PNG or SVG). This is useful for: - Viewing hand-drawn diagrams, sketches, or UI mockups - Getting visual context that text extraction might miss - Implementi…

remarkable_upload

<usecase>Upload a PDF or EPUB file to the reMarkable tablet.</usecase> <instructions> Uploads a local file to the tablet. Only PDF and EPUB formats are supported. Works in all three transports: - Cloud: uploaded via the sync protocol; supports parent_folder + document_name - SSH: transferred over SS…

remarkable_mkdir

<usecase>Create a new folder on the reMarkable tablet.</usecase> <instructions> Creates a folder in the tablet's document hierarchy. In SSH mode the folder appears after xochitl restarts; in cloud mode it syncs to all your devices.

remarkable_move

<usecase>Move a document or folder to a different location.</usecase> <instructions> Moves a document or folder by updating its parent reference in the metadata. Find the document name with remarkable_browse() first.

remarkable_rename

<usecase>Rename a document or folder on the reMarkable tablet.</usecase> <instructions> Changes the display name of a document or folder by updating its metadata. Find the document name with remarkable_browse() first.

remarkable_delete

<usecase>Delete a document or folder on the reMarkable tablet.</usecase> <instructions> DESTRUCTIVE operation. In cloud mode the item is moved to the trash (recoverable from the device's Trash). In SSH mode it is marked deleted in its metadata and disappears from the tablet UI after restart.

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

🔐 secretREMARKABLE_TOKEN"": "${input:remarkable-token}",

configREMARKABLE_USE_SSH

configREMARKABLE_USE_USB_WEB

configREMARKABLE_READ_ONLY

configREMARKABLE_DISABLE_CLOUD_FALLBACKPass --no-cloud-fallback (or set =1) to disable this and fail instead when the device is unreachable.

🔐 secretREMARKABLE_SSH_KEY

configREMARKABLE_BACKGROUND_COLOR"": "#FFFFFF"

configREMARKABLE_OCR_BACKENDSet in your MCP config:

🔐 secretGOOGLE_VISION_API_KEY"": "your-api-key"

configREMARKABLE_ROOT_PATH"": "/Work",

configREMARKABLE_SSH_HOST

configREMARKABLE_SSH_USER

configREMARKABLE_SSH_PORT

🔐 secretREMARKABLE_SSH_PASSWORD

configREMARKABLE_SYNC_WORKERS16 Parallel workers for cloud fetches (clamped to 64).

configREMARKABLE_DISABLE_CACHEunset Set to 1 to disable the on-disk blob cache entirely.

configREMARKABLE_CACHE_MAX_BLOB4194304 (4 MiB) Blobs larger than this are streamed through but not cached.

configREMARKABLE_CACHE_DIR~/.remarkable/cache/blobs Where cached blobs are stored.

configREMARKABLE_RETRY_ATTEMPTS3 Maximum number of request attempts (minimum 1)

configREMARKABLE_RETRY_DELAY2.0 Base delay in seconds for exponential backoff

configREMARKABLE_USB_HOST

configREMARKABLE_USB_TIMEOUT

configREMARKABLE_SKIP_CONFIRM

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — remarkable_canvas (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); my_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); my_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

3 tools perform destructive updates without destructiveHint — remarkable_read deletes at line 400 (tmp_path.unlink(missing_ok=True)); remarkable_recent deletes at line 1128 (tmp_path.unlink(missing_ok=True)); remarkable_image deletes at line 1822 (ocr_tmp_path.unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

13/15 tool handlers declare input schemas (87%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

11/15 tool handlers wrap calls in try/catch (73%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

3 tools have description/behavior mismatches: remarkable_read: description implies read-only but handler writes/deletes/executes; remarkable_recent: description implies read-only but handler writes/deletes/executes; remarkable_image: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 8 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Verified](https://m8ven.ai/badge/mcp/sammorrowdrums/remarkable-mcp?variant=verified)](https://m8ven.ai/mcp/sammorrowdrums/remarkable-mcp)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: e01f799a1b25e8d9bd5ab078ee00a9e806e44d64

code hash: 6f174e5351ba0bbe2ee5bb32009ae65208e021092d309450e554487d45404e91

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client