io.github.shotintoeternity/pocketnook
NPM · @POCKETNOOK/MCP
Deploy repositories or local folders to private Pocketnook URLs from any MCP client.
Available components
Last scanned (21 hours ago)
Scores higher than 79% of npm servers
Category CI/CD and DevOps
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 54 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 663 tokens (~132/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Stability: pass → 0.80 functional
- 3 Oct 26 +1
- Stability: 0.97 → pass security
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/@pocketnook/mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
deploy ~143
Deploy a GitHub repository to a private pocketnook URL and return that URL. With no arguments it deploys the repository the current directory belongs to. pocketnook clones the tip of the default branch from GitHub, so uncommitted or unpushed work is not included — the result says so when that is the case. Redeploying the same repository reuses its existing nook and URL.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Working copy to read the remote from. Defaults to the current directory. |
| repo | string | – | The repository to deploy, as "owner/repo" or a GitHub URL. Omit to use the current directory’s origin remote. |
No output schema declared.
No examples provided.
deploy_directory ~162
Deploy a directory exactly as it is on this machine to a private pocketnook URL, with no git repository required — this uploads the files from disk, including uncommitted work. Use this when there is no repository, or when the local files are what should be deployed; use `deploy` to build what is pushed to GitHub instead. Everything in the directory is sent apart from node_modules, .git and build caches, so any credentials sitting in it go too. Deploying the same nook name again replaces what is there.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | The project directory to upload. Defaults to the current directory. |
| name | string | – | The nook to deploy to. Deploying the same name again updates that nook. Defaults to the directory name. |
No output schema declared.
No examples provided.
list_nooks ~40
List the nooks this account has deployed: name, URL, status, and whether each is private or link-visible. Reads only — it changes nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nook_logs ~74
Show the build output for a nook — the first thing to read when a deploy failed or produced the wrong thing. Reads only — it changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | number | – | How many trailing lines to show. Default 30. |
| nook | string | yes | A nook id, or the repository name like owner/repo. |
No output schema declared.
No examples provided.
stop_nook ~52
Stop serving a nook. The URL, its grants, and its secrets are kept, so deploying again brings it back.
| Name | Type | Req | Description |
|---|---|---|---|
| nook | string | yes | A nook id, or the repository name like owner/repo. |
No output schema declared.
No examples provided.
How do I install the io.github.shotintoeternity/pocketnook MCP server?
io.github.shotintoeternity/pocketnook runs locally as an npm package, launched with npx -y @pocketnook/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pocketnook/mcp
claude mcp add shotintoeternity-pocketnook -- npx -y @pocketnook/mcp
What is the io.github.shotintoeternity/pocketnook MCP server?
io.github.shotintoeternity/pocketnook is an MCP server listed in the public MCP registry as io.github.shotintoeternity/pocketnook. Deploy repositories or local folders to private Pocketnook URLs from any MCP client. This page covers its npm package (@pocketnook/mcp).
Is the io.github.shotintoeternity/pocketnook MCP server safe to use?
io.github.shotintoeternity/pocketnook scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.shotintoeternity/pocketnook MCP server expose?
io.github.shotintoeternity/pocketnook exposes 5 tools: deploy, deploy_directory, list_nooks, nook_logs, stop_nook. Their descriptions and schemas cost roughly 471 tokens of context every time the server is loaded.
Is the io.github.shotintoeternity/pocketnook MCP server still maintained?
io.github.shotintoeternity/pocketnook is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.shotintoeternity/pocketnook MCP server under?
io.github.shotintoeternity/pocketnook declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.