Is Canvas MCP safe to use?

Canvas MCP has an HVTrust score of 87.1/100 (Grade A), ranked #39 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Canvas MCP?

Canvas MCP scores 87.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 228 GitHub stars and is categorized under MCP Servers.

Canvas MCP

vishalsachdev/canvas-mcp

Canvas LMS MCP server — 80+ tools and 5 agent skills for students & educators. Works with Claude, Cursor, Codex, and 40+

MCP Servers Python Grade A Listed MIT

87.1/100

Rank #39 of 1320

Compare Canvas MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-04 · 0d ago

Recent change

No recent signal change

Is Canvas MCP safe? Canvas MCP scores 87.1/100 (Grade A), ranked #39 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.7/10; 72% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#8 LinkedIn MCP Server — 87.3 (A) → #9 Mongodb MCP Server — 87.2 (A) → #11 Hevy MCP Server — 87.1 (A) → #12 Enquire MCP — 86.6 (A) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-08-26

Scorecard Added

OSSF Scorecard: 7.5/10

2026-08-26

Grade Changed

Trust grade B → A

2026-08-26

Rank Moved

Rank rose 93 spots (#141 → #48)

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with another agent Get email alerts for Canvas MCP View MCP Servers Report missing data

73.0

Activity sub-score · out of 100

#10

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

228

Forks

Last Push

2026-09-04

today

Commits (4 wk)

243

Downloads (7d)

552

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #37

Analysis

HVTrust Dimensions vs MCP Servers

87.1 / 100 · 100.0% confidence

Canvas MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.7 / 25

11.1 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

15.0 / 17

3.2 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.8 above avg 12.2

AdoptionLog-scaled stars · package downloads

9.3 / 20

3.0 above avg 6.3

Activity Inputs

73.0 / 100

StarsRepository reach

14.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

8.8 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

7.7 / 10

OpenSSF Scorecard · scanned Sep 1, 2026

Signed Commits

72%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 4

SAST 10

Security-Policy 10

Signed-Releases 8

Token-Permissions 10

Vulnerabilities 10

Is Canvas MCP safe?

Public supply-chain signals for Canvas MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Canvas MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Canvas MCP publish package provenance?

Yes. Canvas MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Canvas MCP have an OpenSSF Scorecard?

Canvas MCP has an OpenSSF Scorecard score of 7.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Canvas MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Canvas MCP use?

Canvas MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Canvas MCP's commits signed?

72% of the last 100 commits to Canvas MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Canvas MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Canvas MCP?

For maintainers

HVTrust scores Canvas MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-26

Scorecard Added

OSSF Scorecard: 7.5/10

2026-08-26

Grade Changed

Trust grade B → A

2026-08-26

Rank Moved

Rank rose 93 spots (#141 → #48)

2026-08-26

HVTrust Changed

HVTrust up 15.4pts (70.5 → 85.9)

2026-08-17

Rank Moved

Rank rose 11 spots (#144 → #133)

2026-08-13

Rank Moved

Rank dropped 10 spots (#128 → #138)

2026-08-08

Newly Listed

First tracked at rank #126

GitHub → PyPI: canvas-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/canvas-mcp.svg)](https://hvtracker.net/agents/canvas-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/canvas-mcp"><img src="https://hvtracker.net/badge/canvas-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON