Mindcache MCP Server

@augmnt-sh/mindcache npm v0.3.1

Published by @augmnt-sh — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 = 96/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 − 4 = 96. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 44

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

  • read_propertiesingests untrusted input
  • add_linkno sensitive capability
  • add_tagno sensitive capability
  • append_to_noteno sensitive capability
  • askno sensitive capability
  • bulk_tagno sensitive capability
  • complete_taskno sensitive capability
  • create_noteno sensitive capability
  • daily_notesno sensitive capability
  • delete_noteno sensitive capability
Show 34 more tools ↓
  • export_noteno sensitive capability
  • extract_linksno sensitive capability
  • find_by_dateno sensitive capability
  • find_by_tagno sensitive capability
  • find_gapsno sensitive capability
  • find_mentionsno sensitive capability
  • find_orphansno sensitive capability
  • find_recentno sensitive capability
  • find_relatedno sensitive capability
  • find_tasksno sensitive capability
  • get_vault_structureno sensitive capability
  • list_tagsno sensitive capability
  • logno sensitive capability
  • log_taskno sensitive capability
  • move_noteno sensitive capability
  • read_noteno sensitive capability
  • read_sectionno sensitive capability
  • read_summaryno sensitive capability
  • read_this_weekno sensitive capability
  • read_todayno sensitive capability
  • reflectno sensitive capability
  • rememberno sensitive capability
  • remember_decisionno sensitive capability
  • remember_ideano sensitive capability
  • remember_learningno sensitive capability
  • remember_meetingno sensitive capability
  • remember_personno sensitive capability
  • remember_referenceno sensitive capability
  • rename_noteno sensitive capability
  • searchno sensitive capability
  • suggest_connectionsno sensitive capability
  • update_propertiesno sensitive capability
  • update_sectionno sensitive capability
  • vault_overviewno 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.3.1 latest A 96/100 0 1.10.0 2026-07-25

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

Use the free API → How scoring works

More in Developer Tools