# jot (mcpb · linux-x64)

Shared, local-first memory for every AI agent, stored as Markdown and versioned in git.

- Trust score: 37/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `osx-x64`: 9/100, [markdown](https://verifymcp.io/servers/arpitk24-jot/jot-darwin-amd64.md), [page](https://verifymcp.io/servers/arpitk24-jot/jot-darwin-amd64)
- mcpb · `osx-arm64`: 9/100, [markdown](https://verifymcp.io/servers/arpitk24-jot/jot-darwin-arm64.md), [page](https://verifymcp.io/servers/arpitk24-jot/jot-darwin-arm64)
- mcpb · `linux-x64`: 37/100 (this document), [markdown](https://verifymcp.io/servers/arpitk24-jot/jot-linux-amd64.md), [page](https://verifymcp.io/servers/arpitk24-jot/jot-linux-amd64)
- mcpb · `linux-arm64`: 8/100, [markdown](https://verifymcp.io/servers/arpitk24-jot/jot-linux-arm64.md), [page](https://verifymcp.io/servers/arpitk24-jot/jot-linux-arm64)
- mcpb · `win-x64`: 8/100, [markdown](https://verifymcp.io/servers/arpitk24-jot/jot-windows-amd64.md), [page](https://verifymcp.io/servers/arpitk24-jot/jot-windows-amd64)
- mcpb · `win-arm64`: 8/100, [markdown](https://verifymcp.io/servers/arpitk24-jot/jot-windows-arm64.md), [page](https://verifymcp.io/servers/arpitk24-jot/jot-windows-arm64)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/ArpitK24/jot/releases/download/v0.1.1/jot-0.1.1-linux-amd64.mcpb`
- Transport: `stdio`
- SHA-256: `b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 448 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "forget" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: 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

### How do I install the jot MCP server?

jot ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/ArpitK24/jot/releases/download/v0.1.1/jot-0.1.1-linux-amd64.mcpb`
- SHA-256: `b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc`

### Verify on macOS / Linux

```bash
echo "b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc  jot-0.1.1-linux-amd64.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\jot-0.1.1-linux-amd64.mcpb).Hash -eq "b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 37)

First indexed and scored.

## MCP tools (5)

### `remember` (~126 tokens)

Save one durable, self-contained memory (a preference, decision, or fact about the user or project) so every agent can use it later.

Input parameters:

- `kind` (string): What sort of memory this is.
- `scope` (string): global (default) for the user, project for this repo only.
- `source` (string): Name of the agent saving this, e.g. claude-code.
- `tags` (array): Short lowercase topic tags, e.g. ["go", "testing"].
- `text` (string, required): The memory itself, one short self-contained statement.

### `recall` (~91 tokens)

Search shared memory for preferences, decisions and facts relevant to the current task. Call this before starting work.

Input parameters:

- `kind` (string): What sort of memory this is.
- `limit` (integer): Max results (default 10).
- `query` (string, required): What you want to know, in plain words.
- `tags` (array): Short lowercase topic tags, e.g. ["go", "testing"].

### `update` (~80 tokens)

Rewrite an existing memory when it has changed. Prefer this over saving a contradicting new one.

Input parameters:

- `id` (string, required): Memory id from recall.
- `kind` (string): What sort of memory this is.
- `tags` (array): Short lowercase topic tags, e.g. ["go", "testing"].
- `text` (string): New text.

### `forget` (~32 tokens)

Delete a memory that is wrong or that the user asked to forget.

Input parameters:

- `id` (string, required): Memory id from recall.

### `list` (~61 tokens)

List the most recent memories, optionally filtered by kind or tags.

Input parameters:

- `kind` (string): What sort of memory this is.
- `limit` (integer)
- `tags` (array): Short lowercase topic tags, e.g. ["go", "testing"].

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/arpitk24-jot/jot-linux-amd64#diagnostics

## Score history

- 2026-11-05: 37
- 2026-11-04: 37

## Common questions

### What is the jot MCP server?

jot is an MCP server listed in the public MCP registry as io.github.ArpitK24/jot. Shared, local-first memory for every AI agent, stored as Markdown and versioned in git. This page covers its MCPB bundle (https://github.com/ArpitK24/jot/releases/download/v0.1.1/jot-0.1.1-linux-amd64.mcpb).

### Is the jot MCP server safe to use?

jot scores 37 out of 100 on VerifyMCP. 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 jot MCP server expose?

jot exposes 5 tools: remember, recall, update, forget, list. Their descriptions and schemas cost roughly 390 tokens of context every time the server is loaded.

### What licence is the jot MCP server under?

jot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the jot MCP server?

VerifyMCP ran 11 checks on jot, covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about jot: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/ArpitK24/jot
- Changelog RSS feed: https://verifymcp.io/servers/arpitk24-jot/jot-linux-amd64.xml
- Changelog JSON feed: https://verifymcp.io/servers/arpitk24-jot/jot-linux-amd64/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/arpitk24-jot/jot-linux-amd64.json
- HTML version of this page: https://verifymcp.io/servers/arpitk24-jot/jot-linux-amd64