Cairn (PyPI) MCP Server

cairn-mcp-server PyPI v0.3.1

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 exposing Cairn's local-first file-organization tools to Claude Code, Codex, Cursor, and any MCP client.

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 2

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

Tool "create_file" can write, overwrite or delete files (keyword "create_file" 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 create_file

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

Tool "create_file" 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 create_file

Tools 48

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

  • create_filewrites files
  • list_dirreads sensitive data
  • add_billno sensitive capability
  • add_person_to_billno sensitive capability
  • add_taskno sensitive capability
  • add_waitingno sensitive capability
  • attentionno sensitive capability
  • complete_taskno sensitive capability
  • create_folderno sensitive capability
  • delete_itemno sensitive capability
Show 38 more tools ↓
  • digest_workspaceno sensitive capability
  • drop_waitingno sensitive capability
  • find_by_metano sensitive capability
  • get_file_tagsno sensitive capability
  • get_file_treeno sensitive capability
  • get_tag_treeno sensitive capability
  • grepno sensitive capability
  • harvest_checklistsno sensitive capability
  • import_documentno sensitive capability
  • import_folderno sensitive capability
  • list_billsno sensitive capability
  • list_paper_projectsno sensitive capability
  • list_tasksno sensitive capability
  • list_templatesno sensitive capability
  • list_waitingno sensitive capability
  • mark_receivedno sensitive capability
  • move_itemno sensitive capability
  • multi_editno sensitive capability
  • next_actionsno sensitive capability
  • preview_paper_recommendationsno sensitive capability
  • project_pulseno sensitive capability
  • read_detailno sensitive capability
  • recommend_papersno sensitive capability
  • recommend_papers_all_projectsno sensitive capability
  • refresh_project_dashboardno sensitive capability
  • reindexno sensitive capability
  • reminder_digestno sensitive capability
  • rename_itemno sensitive capability
  • search_filesno sensitive capability
  • semantic_retrieveno sensitive capability
  • set_statusno sensitive capability
  • settle_billno sensitive capability
  • stale_projectsno sensitive capability
  • update_file_tagsno sensitive capability
  • update_taskno sensitive capability
  • weekly_reviewno sensitive capability
  • who_owesno sensitive capability
  • who_owes_meno sensitive capability

What this scan could not see

Versions 2

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
v0.3.1 latest A 95/100 2 1.13.0 2026-08-25
v0.2.0 A 95/100 2 1.12.1 2026-07-27

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/cairn-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/cairn-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/cairn-mcp-server"><img src="https://mcptrustchecker.com/registry/cairn-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cairn-mcp-server/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 cairn-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Cairn 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in AI, Memory & Reasoning