← remarkable-mcp@2.1.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 74 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 11 caught lines

Download .patch
diff --git a/test_server.py b/test_server.py
--- a/test_server.py
+++ b/test_server.py
@@ -5752,1 +5752,0 @@
-client = SSHClient(key_path="~/.ssh/id_ed25519")
@@ -5756,1 +5755,0 @@
-expected_key = os.path.expanduser("~/.ssh/id_ed25519")
diff --git a/docs/development.md b/docs/development.md
--- a/docs/development.md
+++ b/docs/development.md
@@ -113,1 +113,0 @@
-- **XML-structured docstrings**: use `<usecase>`, `<instructions>`, `<parameters>`, and `<examples>`
@@ -132,1 +131,0 @@
-<instructions>
@@ -134,1 +132,0 @@
-</instructions>
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
--- a/.github/copilot-instructions.md
+++ b/.github/copilot-instructions.md
@@ -158,1 +158,0 @@
-2. **XML-structured docstrings** - Use `<usecase>`, `<instructions>`, `<parameters>`, `<examples>` tags
@@ -169,1 +168,0 @@
-<instructions>
@@ -171,1 +169,0 @@
-</instructions>
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -115,1 +115,0 @@
-<summary>Local directory configuration</summary> Add to `.vscode/mcp.json`: ```json { "servers": { "remarkable": { "command": "uvx", "args": ["remarkable-mcp", 
@@ -575,1 +574,0 @@
-<summary>Google Cloud Vision</summary> 1. Enable [Cloud Vision API](https://console.cloud.google.com/apis/library/vision.googleapis.com) 2. Create an [API key](
diff --git a/remarkable_mcp/cli.py b/remarkable_mcp/cli.py
--- a/remarkable_mcp/cli.py
+++ b/remarkable_mcp/cli.py
@@ -91,1 +91,0 @@
-uvx remarkable-mcp --ssh --ssh-key ~/.ssh/id_ed25519

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.1.0. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: remarkable-mcp: References a credential file in the home directory (KillerSkills verdict caution 74)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 74/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/remarkable-mcp/2.1.0

## Findings with a location
- `test_server.py:5752` · References a credential file in the home directory — test_server.py:5752 · References a credential file in the home directory
- `docs/development.md:134` · Fake instruction boundary tag — docs/development.md:134 · Fake instruction boundary tag · informational: not an instruction file
- `test_server.py:5756` · References a credential file in the home directory — test_server.py:5756 · References a credential file in the home directory
- `.github/copilot-instructions.md:171` · Fake instruction boundary tag — .github/copilot-instructions.md:171 · Fake instruction boundary tag · informational: not an instruction file
- `.github/copilot-instructions.md:169` · Fake instruction boundary tag — .github/copilot-instructions.md:169 · Fake instruction boundary tag · informational: not an instruction file
- `docs/development.md:132` · Fake instruction boundary tag — docs/development.md:132 · Fake instruction boundary tag · informational: not an instruction file
- `README.md:575` · Collapsed <details> block carrying instructions — README.md:575 · Collapsed <details> block carrying instructions
- `docs/development.md:113` · Fake instruction boundary tag — docs/development.md:113 · Fake instruction boundary tag · informational: not an instruction file
- `README.md:115` · Collapsed <details> block carrying instructions — README.md:115 · Collapsed <details> block carrying instructions
- `.github/copilot-instructions.md:158` · Fake instruction boundary tag — .github/copilot-instructions.md:158 · Fake instruction boundary tag · informational: not an instruction file
- `remarkable_mcp/cli.py:91` · References a credential file in the home directory — remarkable_mcp/cli.py:91 · References a credential file in the home directory

## Proposed change
The attached patch removes the 11 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._
# or from a terminal, under your own account:
gh repo fork openclaw/openclaw --clone && cd openclaw
curl -s https://killerskills.ai/skills/pypi/remarkable-mcp/2.1.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/2.1.0 && git commit -am "remarkable-mcp: References a credential file in the home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/remarkable-mcp/2.1.0/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.