jot
MCPB · LINUX-X64 · 6 COMPONENTS
Shared, local-first memory for every AI agent, stored as Markdown and versioned in git.
Last scanned (18 hours ago)
Scores higher than 72% of MCPB servers
Category Memory and Knowledge
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 Security0
- 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.Unverified
- 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).Unverified
- Install-script risk not yet assessed.Unverified
- 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).Unverified
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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 448 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
Checks we ran (11)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)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 scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)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).
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 37
First indexed and scored.
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 5 Nov 2026 · Analysed mcpb/https://github.com/ArpitK24/jot/releases/download/v0.1.1/jot-0.1.1-linux-amd64.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
forget ~32
Delete a memory that is wrong or that the user asked to forget.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory id from recall. |
No output schema declared.
No examples provided.
list ~61
List the most recent memories, optionally filtered by kind or tags.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | What sort of memory this is. |
| limit | integer | – | – |
| tags | array | – | Short lowercase topic tags, e.g. ["go", "testing"]. |
No output schema declared.
No examples provided.
recall ~91
Search shared memory for preferences, decisions and facts relevant to the current task. Call this before starting work.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | What sort of memory this is. |
| limit | integer | – | Max results (default 10). |
| query | string | yes | What you want to know, in plain words. |
| tags | array | – | Short lowercase topic tags, e.g. ["go", "testing"]. |
No output schema declared.
No examples provided.
remember ~126
Save one durable, self-contained memory (a preference, decision, or fact about the user or project) so every agent can use it later.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The memory itself, one short self-contained statement. |
No output schema declared.
No examples provided.
update ~80
Rewrite an existing memory when it has changed. Prefer this over saving a contradicting new one.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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. |
No output schema declared.
No examples provided.
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.
mcpb · linux-x64
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc
macOS / Linux
echo "b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc jot-0.1.1-linux-amd64.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\jot-0.1.1-linux-amd64.mcpb).Hash -eq "b5be41aafe8c9d6fb30587de33edd63159ac8120604766d6f693ad3a90e0d4dc"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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.