Ccontext MCP Server

ccontext-mcp PyPI v0.1.12

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 AI agents to manage project execution context

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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 96 − adoption risk = 94/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 − 3.6 = 96. What the published surface and source actually contain:

PointsWhat was foundCategory
−3.6 Near-miss of @upstash/context7-mcp MTC-SUP-005 supply-chain

2. Client adoption risk — 96 − 2 = 94. 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 1

medium Near-miss of @upstash/context7-mcp (edit distance 2)MTC-SUP-005

"ccontext-mcp" is edit-distance 2 from the high-traffic package "@upstash/context7-mcp". Verify this is the intended package.

Fix: Confirm you meant "@upstash/context7-mcp". Install packages only from their documented, official name.

Location: package ccontext-mcp

Tools 21

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

  • add_noteno sensitive capability
  • add_referenceno sensitive capability
  • clear_statusno sensitive capability
  • commit_updatesno sensitive capability
  • complete_milestoneno sensitive capability
  • create_milestoneno sensitive capability
  • create_taskno sensitive capability
  • delete_taskno sensitive capability
  • get_contextno sensitive capability
  • get_presenceno sensitive capability
Show 11 more tools ↓
  • list_tasksno sensitive capability
  • remove_milestoneno sensitive capability
  • remove_noteno sensitive capability
  • remove_referenceno sensitive capability
  • update_milestoneno sensitive capability
  • update_my_statusno sensitive capability
  • update_noteno sensitive capability
  • update_referenceno sensitive capability
  • update_sketchno sensitive capability
  • update_taskno sensitive capability
  • update_visionno 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.1.12 latest A 94/100 1 1.13.0 2026-08-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 · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ccontext-mcp/badge.svg)](https://mcptrustchecker.com/registry/ccontext-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ccontext-mcp"><img src="https://mcptrustchecker.com/registry/ccontext-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ccontext-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 ccontext-mcp --online --registry pypi

Use the free API → How scoring works

More in AI, Memory & Reasoning