Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.shotintoeternity/pocketnook

NPM · @POCKETNOOK/MCP · SCANNED AUG 17

Deploy repositories or local folders to private Pocketnook URLs from any MCP client.

Available components

70 Trust /100
Trust breakdown (6 categories)

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 →

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
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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @pocketnook/mcp

# add to Claude Code
claude mcp add shotintoeternity-pocketnook -- npx -y @pocketnook/mcp
# add to Codex CLI
codex mcp add shotintoeternity-pocketnook -- npx -y @pocketnook/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shotintoeternity-pocketnook": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pocketnook/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add shotintoeternity-pocketnook --command npx --arg -y --arg @pocketnook/mcp
# ~/.hermes/config.yaml
mcp_servers:
  shotintoeternity-pocketnook:
    command: "npx"
    args: ["-y", "@pocketnook/mcp"]
// mcp.json
{
  "mcpServers": {
    "shotintoeternity-pocketnook": {
      "command": "npx",
      "args": [
        "-y",
        "@pocketnook/mcp"
      ]
    }
  }
}
Changelog

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.

  • 13 Aug 26 70

    First indexed and scored.

Diagnostics

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 17 Aug 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
Dependencies 0 packages
Packages resolved 0
Tree resolution Complete
MCP tools · 5 exposed · ~471 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
directorystringWorking copy to read the remote from. Defaults to the current directory.
repostringThe 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.

NameTypeReqDescription
directorystringThe project directory to upload. Defaults to the current directory.
namestringThe 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.

NameTypeReqDescription
linesnumberHow many trailing lines to show. Default 30.
nookstringyesA 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.

NameTypeReqDescription
nookstringyesA nook id, or the repository name like owner/repo.

No output schema declared.

No examples provided.