GraphCanon
Home/MCPControl/Trust report

Trust and health report

MCPControl - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated today · GitHub synced today

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Slowing36% signal

last push 220d ago · last release 1y

Provenance

Repository identity and fork provenance (github_public_v1).

Security scan

Dependency advisory security scan when a lockfile is present. Not a full code audit.

Status
10 low
Last scan
today
Scanner
osv@v1

Findings

GHSA-f886-m6hf-6m8v
brace-expansion@1.1.12 · package-lock.json
GHSA-23c5-xmqv-rm74
minimatch@3.1.2 · package-lock.json
GHSA-3ppc-4f35-3m26
minimatch@3.1.2 · package-lock.json
GHSA-7r86-cg39-jmmj
minimatch@3.1.2 · package-lock.json
GHSA-v6h2-p8h4-qcjw
brace-expansion@1.1.11 · package-lock.json
GHSA-xffm-g5w8-qvg7
@eslint/plugin-kit@0.3.1 · package-lock.json
GHSA-345p-7cg4-v4c7
@modelcontextprotocol/sdk@1.16.0 · package-lock.json
GHSA-8r9q-7v3j-jr4g
@modelcontextprotocol/sdk@1.16.0 · package-lock.json
GHSA-w48q-cv73-mx4w
@modelcontextprotocol/sdk@1.16.0 · package-lock.json
GHSA-2g4f-4pwh-qvx6
ajv@6.12.6 · package-lock.json

Method and caveats:these are sourced, dated heuristics from public GitHub data and optional dependency scans. A status like "no criticals found on 2026-07-11" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/claude-did-this-mcpcontrol/trust.

Common questions

Is MCPControl maintained?
GraphCanon rates MCPControl "Slowing" (36% maintenance signal from public GitHub metadata, computed today). Last push was 220 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is MCPControl safe to use?
Last scanned today (deps profile). Status: 10 low - 10 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify MCPControl as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is MCPControl a fork?
No. MCPControl is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does MCPControl have known security vulnerabilities?
Last scanned today (deps profile). Status: 10 low - 10 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
How often is the MCPControl trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).
What does GraphCanon never claim about MCPControl?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for MCPControl. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for MCPControl?
Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.