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

F
Warning
24/100

praveensehgal/remarkable-mcp

MCP server that connects AI assistants to your reMarkable tablet, enabling reading, searching, and traversing handwritten and typed notes via OCR.

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 pushwhy connect →

Who stands behind it

praveensehgal

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 →

Install from

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 374: tmp_path.unlink(missing_ok=True)); remarkable_recent (line 1082: tmp_path.unlink(missing_ok=True)); remarkable_image (line 1594: 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 3 credentials: GOOGLE_VISION_API_KEY, REMARKABLE_TOKEN, REMARKABLE_SSH_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configREMARKABLE_USE_SSH
🔐 secretGOOGLE_VISION_API_KEY"": "your-api-key"
configREMARKABLE_OCR_BACKENDSet in your MCP config:
configREMARKABLE_ROOT_PATH"": "/Work",
configREMARKABLE_USB_HOST
configREMARKABLE_SSH_HOST
configREMARKABLE_SSH_USER
configREMARKABLE_SSH_PORT
🔐 secretREMARKABLE_TOKEN"": "${input:remarkable-token}",
configREMARKABLE_USE_USB_WEB
configREMARKABLE_BACKGROUND_COLOR"": "#FFFFFF"
🔐 secretREMARKABLE_SSH_PASSWORD
configREMARKABLE_HOST"": "http://YOUR_TABLET_IP"
configREMARKABLE_USB_TIMEOUT
// quality suggestions

Tool annotations

4/13 tools have annotations

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

All four hints declared on every tool

13/13 tools missing one or more hints — remarkable_read (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remarkable_browse (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remarkable_recent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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 374 (tmp_path.unlink(missing_ok=True)); remarkable_recent deletes at line 1082 (tmp_path.unlink(missing_ok=True)); remarkable_image deletes at line 1594 (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

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

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

Tool inputs are validated

11/13 tool handlers declare input schemas (85%)

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

Tool handlers catch errors

10/13 tool handlers wrap calls in try/catch (77%)

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/praveensehgal/remarkable-mcp?variant=verified)](https://m8ven.ai/mcp/praveensehgal/remarkable-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: d385834dbc80ebef2f61b8fe898c84288fc605a1
code hash: 70287fd3873b3eb94955f79876ac39229e6496588b40e0dd5cbbf5d2a29a803f
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