Flint Note MCP Server

@flint-note/server npm v0.10.2

Published by @flint-note — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Agent-first note-taking application with MCP server

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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 = 98/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 − 2 = 98. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

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

  • Available note typesno sensitive capability
  • bulk_delete_notesno sensitive capability
  • create_noteno sensitive capability
  • create_note_typeno sensitive capability
  • create_vaultno sensitive capability
  • delete_noteno sensitive capability
  • delete_note_typeno sensitive capability
  • find_broken_linksno sensitive capability
  • get_backlinksno sensitive capability
  • get_current_vaultno sensitive capability
Show 27 more tools ↓
  • get_noteno sensitive capability
  • get_note_infono sensitive capability
  • get_note_linksno sensitive capability
  • get_note_type_infono sensitive capability
  • get_notesno sensitive capability
  • Incoming links to noteno sensitive capability
  • Individual noteno sensitive capability
  • Individual note in specific vaultno sensitive capability
  • list_note_typesno sensitive capability
  • list_notes_by_typeno sensitive capability
  • list_vaultsno sensitive capability
  • migrate_linksno sensitive capability
  • Notes by tagno sensitive capability
  • Notes by typeno sensitive capability
  • Notes by type in specific vaultno sensitive capability
  • Recently modified notesno sensitive capability
  • remove_vaultno sensitive capability
  • rename_noteno sensitive capability
  • search_by_linksno sensitive capability
  • search_notesno sensitive capability
  • search_notes_advancedno sensitive capability
  • search_notes_sqlno sensitive capability
  • switch_vaultno sensitive capability
  • update_noteno sensitive capability
  • update_note_typeno sensitive capability
  • update_vaultno sensitive capability
  • Workspace statisticsno sensitive capability

What this scan could not see

Versions 1

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.10.2 latest A 98/100 0 1.13.0 2026-09-07

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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/flint-note-server/badge.svg)](https://mcptrustchecker.com/registry/flint-note-server)
HTML
<a href="https://mcptrustchecker.com/registry/flint-note-server"><img src="https://mcptrustchecker.com/registry/flint-note-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/flint-note-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 @flint-note/server --online

Use the free API → How scoring works

More in AI, Memory & Reasoning