Is Codex Tldraw MCP safe to use?

Codex Tldraw MCP has an HVTrust score of 74.0/100 (Grade B), ranked #286 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Codex Tldraw MCP?

Codex Tldraw MCP scores 74.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 25 GitHub stars and is categorized under MCP Servers.

Codex Tldraw MCP

Repository

Local Codex MCP server for scanning repositories and writing tldraw product workflow diagrams.

MCP Servers TypeScript Listed MIT

Is Codex Tldraw MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.8 / 10

Provenance Attested

Signed commits 100%

Last push 8d ago

Advisories None known

Compare Codex Tldraw MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Codex Tldraw MCP scores 74.0/100 (Grade B), ranked #286 of 1374 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 4.8/10; 100% of recent commits are signed; no published advisory affects its latest release (codex-tldraw-mcp); last pushed 2026-11-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Codex Tldraw MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 4.8 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +8.8 → 82.8 A · #57 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Codex Tldraw MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/jananadiw/codex-tldraw-mcp, MIT, last pushed 2026-11-02. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.8/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection4
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 3

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0
Published packages Linked and attested
- npm codex-tldraw-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: codex-tldraw-mcp 0.7.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-30 OSSF Scorecard: 4.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Codex Tldraw MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Codex Tldraw MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Codex Tldraw MCP’s 74.0.

Where the 74.0 comes from

HVTrust dimensions vs the MCP Servers average

74.0 / 100 · 100.0% confidence

Codex Tldraw MCP MCP Servers average (778 agents)

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

18.5 / 25

7.7 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

12.4 / 20

in line with avg 12.2

AdoptionLog-scaled stars · package downloads

6.8 / 20

0.8 below avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-09

Rank Moved

Rank dropped 13 spots (#264 → #277)

2026-11-08

Rank Moved

Rank dropped 33 spots (#231 → #264)

2026-11-07

Rank Moved

Rank dropped 17 spots (#214 → #231)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent View MCP Servers Report missing data

38.5

Activity sub-score · out of 100

#168

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 B 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-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-02

8 days ago

Commits (4 wk)

Downloads (7d)

336

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼9

was #277

Analysis

Activity Inputs

38.5 / 100

StarsRepository reach

8.5 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

0.0 / 20

Common questions about Codex Tldraw MCP

Codex Tldraw MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Codex Tldraw MCP publish package provenance?

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

Does Codex Tldraw MCP have an OpenSSF Scorecard?

Codex Tldraw MCP has an OpenSSF Scorecard score of 4.8/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 Codex Tldraw MCP actively maintained?

Maintained. Last push was 8 days ago.

What license does Codex Tldraw MCP use?

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

Are Codex Tldraw MCP's commits signed?

100% of the last 100 commits to Codex Tldraw 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

Codex Tldraw MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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

How this surface has changed

Detected changes to Codex Tldraw MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-09

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Codex Tldraw MCP?

For maintainers

HVTrust scores Codex Tldraw 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-11-09

Rank Moved

Rank dropped 13 spots (#264 → #277)

2026-11-08

Rank Moved

Rank dropped 33 spots (#231 → #264)

2026-11-07

Rank Moved

Rank dropped 17 spots (#214 → #231)

2026-10-31

Rank Moved

Rank rose 16 spots (#219 → #203)

2026-10-27

Rank Moved

Rank rose 15 spots (#227 → #212)

2026-10-12

Rank Moved

Rank rose 10 spots (#204 → #194)

2026-10-10

Rank Moved

Rank rose 44 spots (#254 → #210)

2026-10-09

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-10-09

Rank Moved

Rank dropped 12 spots (#242 → #254)

2026-10-08

Rank Moved

Rank rose 29 spots (#271 → #242)

2026-10-08

Activity Score Changed

Activity score up 10pts (36 → 46)

2026-10-05

Rank Moved

Rank dropped 28 spots (#241 → #269)

2026-10-03

Rank Moved

Rank dropped 17 spots (#220 → #237)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 718 spots (#909 → #191)

2026-09-23

HVTrust Changed

HVTrust up 49.9pts (26.6 → 76.5)

2026-09-22

Newly Listed

First tracked at rank #909

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-15

Rank Moved

Rank rose 28 spots (#211 → #183)

2026-09-13

Rank Moved

Rank dropped 14 spots (#192 → #206)

2026-09-12

Rank Moved

Rank rose 43 spots (#235 → #192)

2026-09-06

Rank Moved

Rank dropped 39 spots (#186 → #225)

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 609 spots (#795 → #186)

2026-09-05

HVTrust Changed

HVTrust up 26.3pts (49.5 → 75.8)

2026-09-04

Grade Changed

Trust grade B → D

2026-09-04

Rank Moved

Rank dropped 649 spots (#146 → #795)

2026-09-04

HVTrust Changed

HVTrust down 25.9pts (75.4 → 49.5)

2026-09-02

Grade Changed

Trust grade C → B

2026-09-02

Rank Moved

Rank rose 514 spots (#653 → #139)

2026-09-02

HVTrust Changed

HVTrust up 24.6pts (50.9 → 75.5)

2026-09-01

Rank Moved

Rank dropped 22 spots (#631 → #653)

2026-08-31

Rank Moved

Rank dropped 37 spots (#594 → #631)

2026-08-30

Scorecard Added

OSSF Scorecard: 4.1/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 109 spots (#703 → #594)

2026-08-30

HVTrust Changed

HVTrust up 5.6pts (45.5 → 51.1)

2026-08-29

Rank Moved

Rank dropped 46 spots (#657 → #703)

2026-08-27

Rank Moved

Rank dropped 17 spots (#644 → #661)

2026-08-26

Rank Moved

Rank dropped 101 spots (#543 → #644)

2026-08-24

Rank Moved

Rank dropped 10 spots (#529 → #539)

2026-08-13

Rank Moved

Rank dropped 12 spots (#514 → #526)

GitHub → npm: codex-tldraw-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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

Codex Tldraw MCP

How Codex Tldraw MCP could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Codex Tldraw MCP compares in MCP Servers

Where the 74.0 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Codex Tldraw MCP

AI agent surface

Maintain Codex Tldraw MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers