Context Manager (asd412id) MCP Server

@asd412id/mcp-context-manager npm v1.0.17 Source verified

Published by asd412id — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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 = 97/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 − 3 = 97. 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

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 1

low Unconstrained path parameter "path" on "file_list_dir"MTC-CAP-008

Tool "file_list_dir" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool file_list_dir · inputSchema.properties.path

Tools 36

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

  • file_list_dirreads sensitive data
  • checkpoint_compareno sensitive capability
  • checkpoint_deleteno sensitive capability
  • checkpoint_listno sensitive capability
  • checkpoint_loadno sensitive capability
  • checkpoint_saveno sensitive capability
  • context_get_summaryno sensitive capability
  • context_list_summariesno sensitive capability
  • context_merge_summariesno sensitive capability
  • context_prune_smartno sensitive capability
Show 26 more tools ↓
  • context_statusno sensitive capability
  • context_summarizeno sensitive capability
  • file_infono sensitive capability
  • file_search_contentno sensitive capability
  • file_smart_readno sensitive capability
  • memory_capture_candidatesno sensitive capability
  • memory_cleanupno sensitive capability
  • memory_clearno sensitive capability
  • memory_deleteno sensitive capability
  • memory_getno sensitive capability
  • memory_listno sensitive capability
  • memory_searchno sensitive capability
  • memory_setno sensitive capability
  • memory_updateno sensitive capability
  • project_detectno sensitive capability
  • session_handoffno sensitive capability
  • session_initno sensitive capability
  • store_healthno sensitive capability
  • tracker_cleanupno sensitive capability
  • tracker_exportno sensitive capability
  • tracker_getno sensitive capability
  • tracker_logno sensitive capability
  • tracker_searchno sensitive capability
  • tracker_set_projectno sensitive capability
  • tracker_statusno sensitive capability
  • tracker_todo_updateno 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
v1.0.17 latest A 97/100 1 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 · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/asd412id-mcp-context-manager/badge.svg)](https://mcptrustchecker.com/registry/asd412id-mcp-context-manager)
HTML
<a href="https://mcptrustchecker.com/registry/asd412id-mcp-context-manager"><img src="https://mcptrustchecker.com/registry/asd412id-mcp-context-manager/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/asd412id-mcp-context-manager/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 @asd412id/mcp-context-manager --online

Use the free API → How scoring works

Other implementations of Context Manager 1

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

More in Developer Tools