Keepsake MCP Server

keepsake-mcp npm v1.10.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for Keepsake personal CRM — connect your AI agent to your contacts, tasks, notes, and more

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 14

medium Tool "unlink_tag" can modify the filesystemMTC-CAP-002

Tool "unlink_tag" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_tag

medium Tool "unlink_note_contact" can modify the filesystemMTC-CAP-002

Tool "unlink_note_contact" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_note_contact

medium Tool "unlink_entry_contact" can modify the filesystemMTC-CAP-002

Tool "unlink_entry_contact" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_entry_contact

medium Tool "unlink_task_contact" can modify the filesystemMTC-CAP-002

Tool "unlink_task_contact" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_task_contact

medium Tool "unlink_task_note" can modify the filesystemMTC-CAP-002

Tool "unlink_task_note" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_task_note

medium Tool "unlink_notes" can modify the filesystemMTC-CAP-002

Tool "unlink_notes" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_notes

medium Tool "unlink_note_date" can modify the filesystemMTC-CAP-002

Tool "unlink_note_date" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_note_date

low Mutating tool "unlink_tag" declares no destructiveHintMTC-CAP-005

Tool "unlink_tag" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_tag

low Mutating tool "unlink_note_contact" declares no destructiveHintMTC-CAP-005

Tool "unlink_note_contact" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_note_contact

low Mutating tool "unlink_entry_contact" declares no destructiveHintMTC-CAP-005

Tool "unlink_entry_contact" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_entry_contact

low Mutating tool "unlink_task_contact" declares no destructiveHintMTC-CAP-005

Tool "unlink_task_contact" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_task_contact

low Mutating tool "unlink_task_note" declares no destructiveHintMTC-CAP-005

Tool "unlink_task_note" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_task_note

low Mutating tool "unlink_notes" declares no destructiveHintMTC-CAP-005

Tool "unlink_notes" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_notes

low Mutating tool "unlink_note_date" declares no destructiveHintMTC-CAP-005

Tool "unlink_note_date" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_note_date

Tools 73

Each tool and what it can reach — statically extracted from the published source.

  • unlink_entry_contactwrites files
  • unlink_note_contactwrites files
  • unlink_note_datewrites files
  • unlink_noteswrites files
  • unlink_tagwrites files
  • unlink_task_contactwrites files
  • unlink_task_notewrites files
  • archive_noteno sensitive capability
  • complete_taskno sensitive capability
  • create_companyno sensitive capability
Show 63 more tools ↓
  • create_contactno sensitive capability
  • create_day_blockno sensitive capability
  • create_entryno sensitive capability
  • create_noteno sensitive capability
  • create_note_commentno sensitive capability
  • create_tagno sensitive capability
  • create_taskno sensitive capability
  • create_task_headerno sensitive capability
  • delete_companyno sensitive capability
  • delete_contactno sensitive capability
  • delete_day_blockno sensitive capability
  • delete_entryno sensitive capability
  • delete_noteno sensitive capability
  • delete_note_commentno sensitive capability
  • delete_tagno sensitive capability
  • delete_taskno sensitive capability
  • delete_task_headerno sensitive capability
  • get_agent_instructionsno sensitive capability
  • get_changelogno sensitive capability
  • get_companyno sensitive capability
  • get_contactno sensitive capability
  • get_contact_timelineno sensitive capability
  • get_dayno sensitive capability
  • get_noteno sensitive capability
  • get_tagno sensitive capability
  • get_tag_itemsno sensitive capability
  • get_task_headerno sensitive capability
  • get_tasks_overdueno sensitive capability
  • get_tasks_todayno sensitive capability
  • link_entry_contactno sensitive capability
  • link_note_contactno sensitive capability
  • link_note_dateno sensitive capability
  • link_notesno sensitive capability
  • link_tagno sensitive capability
  • link_task_contactno sensitive capability
  • link_task_noteno sensitive capability
  • list_companiesno sensitive capability
  • list_contactsno sensitive capability
  • list_day_blocksno sensitive capability
  • list_daysno sensitive capability
  • list_entriesno sensitive capability
  • list_note_commentsno sensitive capability
  • list_notesno sensitive capability
  • list_tagsno sensitive capability
  • list_task_headersno sensitive capability
  • list_tasksno sensitive capability
  • pin_noteno sensitive capability
  • restore_noteno sensitive capability
  • searchno sensitive capability
  • search_companiesno sensitive capability
  • search_contactsno sensitive capability
  • snooze_taskno sensitive capability
  • uncomplete_taskno sensitive capability
  • update_companyno sensitive capability
  • update_contactno sensitive capability
  • update_dayno sensitive capability
  • update_day_blockno sensitive capability
  • update_entryno sensitive capability
  • update_noteno sensitive capability
  • update_note_commentno sensitive capability
  • update_tagno sensitive capability
  • update_taskno sensitive capability
  • update_task_headerno sensitive capability

What this scan could not see

Versions 9

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.10.0 latest A 95/100 14 1.13.0 2026-09-07
v1.9.1 A 95/100 12 1.13.0 2026-09-06
v1.9.0 A 95/100 12 1.13.0 2026-09-01
v1.8.0 A 95/100 12 1.12.1 2026-08-22
v1.7.0 A 95/100 12 1.12.1 2026-08-12
Show 4 more versions ↓
v1.6.0 A 95/100 12 1.12.1 2026-08-10
v1.5.0 A 95/100 12 1.12.1 2026-08-03
v1.4.0 A 95/100 12 1.12.1 2026-08-01
v1.3.0 A 98/100 1 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/keepsake-mcp/badge.svg)](https://mcptrustchecker.com/registry/keepsake-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/keepsake-mcp"><img src="https://mcptrustchecker.com/registry/keepsake-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/keepsake-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan keepsake-mcp --online

Use the free API → How scoring works

More in Business & CRM