kinjot-mcpBLOCK
jotnow - Save useful agent outputs
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Keep what your AI coding agent figures out. Tell Claude Code or Codex to "jot that down", and the note lands in your Kinjot account, tagged and searchable.
- Works with Claude Code, Codex and any other MCP client, plus a terminal CLI.
- Free to sign up and use. Export every note as Markdown whenever you like.
- Saves notes only when you ask. Agents can send brief Inbox notifications under the narrow rules below.
Documentation · Claude Code setup · Codex setup · MCP tool reference
Quick start
- Sign up at kinjot.com (free) and confirm your email.
- Open Settings > API keys and create a key.
- Install the CLI and save your key:
npm install --global kinjot kinjot key
kinjot key asks for the key, checks it, and saves it to ~/.kinjot/config.json. Only your user can read that file. It then prints the setup for your MCP client.
- Connect your agent:
# Claude Code (add -s user to use it in every project) claude mcp add kinjot -- npx -y kinjot # Codex codex mcp add kinjot -- npx -y kinjot
- Tell your agent to "jot that down". Later, ask it to find your jots about
something, or to show your recent jots.
What your agent can do
39cd4ddd80c7OBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add kinjot --env KINJOT_API_KEY=${KINJOT_API_KEY} -- npx -y [email protected]Exposed tools (11)
9 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
append_to_jot | read | |
edit_jot | write | |
example | read | A tool |
find_jots | read | |
get_jot | read | |
inbox | read | |
jot | read | |
list_recent_jots | read | |
notify | read | |
recall_jots | read | |
upload_image | write |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- declared (1 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (13)
exec(sql: string): void;
[`import { png } from '../../core/src/image-bytes-fixtures.js';`],[`export * from '../../core/src/index.js';`],
[`const m = await import('../../../scripts/x.mjs');`],[`vi.mock('../../core/src/index.js', () => ({}));`],[`readFileSync(new URL('../../../docs/x.md', import.meta.url));`],const API_URL = 'http://127.0.0.1:9/functions/v1/mcp-api';
const url = 'http://127.0.0.1:54321/custom/path?owner=o-neil&mode=1';
const projectUrl = 'http://127.0.0.1:54321/functions/v1/mcp-api?mode=test';
KINJOT_API_URL: 'http://127.0.0.1:54321/functions/v1/mcp-api',
expect(config.apiUrl).toBe('http://127.0.0.1:54321/functions/v1/mcp-api');@modelcontextprotocol/sdk, zod, @types/node, typescript, vitest
2. Open **Settings > API keys** and create a key.
Gates applied: no_behavioural_pass.
39cd4ddd80c7full audit observations/trust-audit/mcp-server/zainzaidi37__kinjot-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | 39cd4ddd80c7 | BLOCK | D | 69 | first audit |
Questions
What is the kinjot-mcp MCP server?
jotnow - Save useful agent outputs
What tools does kinjot-mcp expose?
11 in total: 9 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is kinjot-mcp safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on.
What credentials does kinjot-mcp need?
It reads KINJOT_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does kinjot-mcp run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as kinjot at 0.1.5.
How current is this page?
The grade is for one exact copy of the source (39cd4ddd80c7), read on 2026-10-11. The repository is watched and re-audited when it changes.