Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.debu-sinha/excalidraw

NPM · EXCALIDRAW-MCP-SERVER · SCANNED SEP 25

Security-hardened Excalidraw MCP server with auth, rate limiting, and 14 tools

Available components

npm · excalidraw-mcp-server 76
0 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects nanoid 3.3.3, reached via @excalidraw/excalidraw > nanoid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 460 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 229 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 649 tokens (~46/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_element" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.debu-sinha/excalidraw MCP server?

io.github.debu-sinha/excalidraw runs locally as an npm package, launched with npx -y excalidraw-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · excalidraw-mcp-server

# add to Claude Code
claude mcp add debu-sinha-excalidraw -- npx -y excalidraw-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "debu-sinha-excalidraw": {
      "command": "npx",
      "args": [
        "-y",
        "excalidraw-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "debu-sinha-excalidraw": {
      "command": "npx",
      "args": [
        "-y",
        "excalidraw-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add debu-sinha-excalidraw -- npx -y excalidraw-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "debu-sinha-excalidraw": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "excalidraw-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add debu-sinha-excalidraw --command npx --arg -y --arg excalidraw-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  debu-sinha-excalidraw:
    command: "npx"
    args: ["-y", "excalidraw-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "debu-sinha-excalidraw": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "excalidraw-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add debu-sinha-excalidraw -t stdio -c npx -a -y excalidraw-mcp-server
// mcp.json
{
  "mcpServers": {
    "debu-sinha-excalidraw": {
      "command": "npx",
      "args": [
        "-y",
        "excalidraw-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • CVE-2026-65902 affects this package: high ▼ security
    • CVE-2026-65913 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-65914 affects this package: high ▼ security
    • CVE-2026-41239 affects this package: high ▼ security
    • CVE-2026-75838 affects this package: high ▼ security
    • CVE-2026-49459 affects this package: high ▼ security
    • CVE-2026-65903 affects this package: high ▼ security
    • CVE-2026-41238 affects this package: high ▼ security
    • CVE-2026-41159 affects this package: high ▼ security
    • CVE-2025-26791 affects this package: high ▼ security
    • CVE-2026-0540 affects this package: high ▼ security
    • CVE-2026-67213 affects this package: high ▼ security
    • CVE-2026-73086 affects this package: high ▼ security
    • CVE-2025-15599 affects this package: high ▼ security
    • CVE-2024-55565 affects this package: high ▼ security
    • CVE-2026-41148 affects this package: high ▼ security
    • CVE-2026-41150 affects this package: high ▼ security
    • CVE-2026-65912 affects this package: high ▼ security
    • CVE-2026-50159 affects this package: high ▼ security
    • CVE-2026-65899 affects this package: high ▼ security
    • CVE-2026-66010 affects this package: high ▼ security
    • CVE-2026-71438 affects this package: high ▼ security
    • CVE-2026-65898 affects this package: high ▼ security
    • CVE-2026-65900 affects this package: high ▼ security
    • CVE-2026-41149 affects this package: high ▼ security
    • CVE-2026-41240 affects this package: high ▼ security
    • CVE-2026-71436 affects this package: high ▼ security
    • CVE-2026-49458 affects this package: high ▼ security
    • CVE-2026-49978 affects this package: high ▼ security
    • CVE-2026-67214 affects this package: high ▼ security
  • 23 Sept 26 −1
    • CVE-2026-65902 affects this package: high ▼ security
    • CVE-2026-65913 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-65914 affects this package: high ▼ security
    • CVE-2026-41239 affects this package: high ▼ security
    • CVE-2026-75838 affects this package: high ▼ security
    • CVE-2026-49459 affects this package: high ▼ security
    • CVE-2026-65903 affects this package: high ▼ security
    • CVE-2026-41238 affects this package: high ▼ security
    • CVE-2026-41159 affects this package: high ▼ security
    • CVE-2025-26791 affects this package: high ▼ security
    • CVE-2026-0540 affects this package: high ▼ security
    • CVE-2026-67213 affects this package: high ▼ security
    • CVE-2026-73086 affects this package: high ▼ security
    • CVE-2025-15599 affects this package: high ▼ security
    • CVE-2024-55565 affects this package: high ▼ security
    • CVE-2026-41148 affects this package: high ▼ security
    • CVE-2026-41150 affects this package: high ▼ security
    • CVE-2026-65912 affects this package: high ▼ security
    • CVE-2026-50159 affects this package: high ▼ security
    • CVE-2026-65899 affects this package: high ▼ security
    • CVE-2026-66010 affects this package: high ▼ security
    • CVE-2026-71438 affects this package: high ▼ security
    • CVE-2026-65898 affects this package: high ▼ security
    • CVE-2026-65900 affects this package: high ▼ security
    • CVE-2026-41149 affects this package: high ▼ security
    • CVE-2026-41240 affects this package: high ▼ security
    • CVE-2026-71436 affects this package: high ▼ security
    • CVE-2026-49458 affects this package: high ▼ security
    • CVE-2026-49978 affects this package: high ▼ security
    • CVE-2026-67214 affects this package: high ▼ security
    • Known CVEs: partial → fail ▼ security
  • 22 Sept 26 +2
    • Known CVEs: fail → partial ▲ security
  • 21 Sept 26 +1
    • CVE-2026-65902 affects this package: high ▼ security
    • CVE-2026-65913 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-65914 affects this package: high ▼ security
    • CVE-2026-41239 affects this package: high ▼ security
    • CVE-2026-75838 affects this package: high ▼ security
    • CVE-2026-49459 affects this package: high ▼ security
    • CVE-2026-65903 affects this package: high ▼ security
    • CVE-2026-41238 affects this package: high ▼ security
    • CVE-2026-41159 affects this package: high ▼ security
    • CVE-2025-26791 affects this package: high ▼ security
    • CVE-2026-0540 affects this package: high ▼ security
    • CVE-2026-67213 affects this package: high ▼ security
    • CVE-2026-73086 affects this package: high ▼ security
    • CVE-2025-15599 affects this package: high ▼ security
    • CVE-2024-55565 affects this package: high ▼ security
    • CVE-2026-41148 affects this package: high ▼ security
    • CVE-2026-41150 affects this package: high ▼ security
    • CVE-2026-65912 affects this package: high ▼ security
    • CVE-2026-50159 affects this package: high ▼ security
    • CVE-2026-65899 affects this package: high ▼ security
    • CVE-2026-66010 affects this package: high ▼ security
    • CVE-2026-71438 affects this package: high ▼ security
    • CVE-2026-65898 affects this package: high ▼ security
    • CVE-2026-65900 affects this package: high ▼ security
    • CVE-2026-41149 affects this package: high ▼ security
    • CVE-2026-41240 affects this package: high ▼ security
    • CVE-2026-71436 affects this package: high ▼ security
    • CVE-2026-49458 affects this package: high ▼ security
    • CVE-2026-49978 affects this package: high ▼ security
    • CVE-2026-67214 affects this package: high ▼ security
  • 20 Sept 26 0
    • CVE-2026-65902 affects this package: high ▼ security
    • CVE-2026-65913 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-65914 affects this package: high ▼ security
    • CVE-2026-41239 affects this package: high ▼ security
    • CVE-2026-75838 affects this package: high ▼ security
    • CVE-2026-49459 affects this package: high ▼ security
    • CVE-2026-65903 affects this package: high ▼ security
    • CVE-2026-41238 affects this package: high ▼ security
    • CVE-2026-41159 affects this package: high ▼ security
    • CVE-2025-26791 affects this package: high ▼ security
    • CVE-2026-0540 affects this package: high ▼ security
    • CVE-2026-67213 affects this package: high ▼ security
    • CVE-2026-73086 affects this package: high ▼ security
    • CVE-2025-15599 affects this package: high ▼ security
    • CVE-2024-55565 affects this package: high ▼ security
    • CVE-2026-41148 affects this package: high ▼ security
    • CVE-2026-41150 affects this package: high ▼ security
    • CVE-2026-65912 affects this package: high ▼ security
    • CVE-2026-50159 affects this package: high ▼ security
    • CVE-2026-65899 affects this package: high ▼ security
    • CVE-2026-66010 affects this package: high ▼ security
    • CVE-2026-71438 affects this package: high ▼ security
    • CVE-2026-65898 affects this package: high ▼ security
    • CVE-2026-65900 affects this package: high ▼ security
    • CVE-2026-41149 affects this package: high ▼ security
    • CVE-2026-41240 affects this package: high ▼ security
    • CVE-2026-71436 affects this package: high ▼ security
    • CVE-2026-49458 affects this package: high ▼ security
    • CVE-2026-49978 affects this package: high ▼ security
    • CVE-2026-67214 affects this package: high ▼ security
  • 19 Sept 26 −3
    • CVE-2026-65902 affects this package: high ▼ security
    • CVE-2026-65913 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-65914 affects this package: high ▼ security
    • CVE-2026-41239 affects this package: high ▼ security
    • CVE-2026-75838 affects this package: high ▼ security
    • CVE-2026-49459 affects this package: high ▼ security
    • CVE-2026-65903 affects this package: high ▼ security
    • CVE-2026-41238 affects this package: high ▼ security
    • CVE-2026-41159 affects this package: high ▼ security
    • CVE-2025-26791 affects this package: high ▼ security
    • CVE-2026-0540 affects this package: high ▼ security
    • CVE-2026-67213 affects this package: high ▼ security
    • CVE-2026-73086 affects this package: high ▼ security
    • CVE-2025-15599 affects this package: high ▼ security
    • CVE-2024-55565 affects this package: high ▼ security
    • CVE-2026-41148 affects this package: high ▼ security
    • CVE-2026-41150 affects this package: high ▼ security
    • CVE-2026-65912 affects this package: high ▼ security
    • CVE-2026-50159 affects this package: high ▼ security
    • CVE-2026-65899 affects this package: high ▼ security
    • CVE-2026-66010 affects this package: high ▼ security
    • CVE-2026-71438 affects this package: high ▼ security
    • CVE-2026-65898 affects this package: high ▼ security
    • CVE-2026-65900 affects this package: high ▼ security
    • CVE-2026-41149 affects this package: high ▼ security
    • CVE-2026-41240 affects this package: high ▼ security
    • CVE-2026-71436 affects this package: high ▼ security
    • CVE-2026-49458 affects this package: high ▼ security
    • CVE-2026-49978 affects this package: high ▼ security
    • CVE-2026-67214 affects this package: high ▼ security
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • CVE-2026-65902 affects this package: high ▼ security
    • CVE-2026-65913 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-65914 affects this package: high ▼ security
    • CVE-2026-41239 affects this package: high ▼ security
    • CVE-2026-75838 affects this package: high ▼ security
    • CVE-2026-49459 affects this package: high ▼ security
    • CVE-2026-65903 affects this package: high ▼ security
    • CVE-2026-41238 affects this package: high ▼ security
    • CVE-2026-41159 affects this package: high ▼ security
    • CVE-2025-26791 affects this package: high ▼ security
    • CVE-2026-0540 affects this package: high ▼ security
    • CVE-2026-67213 affects this package: high ▼ security
    • CVE-2026-73086 affects this package: high ▼ security
    • CVE-2025-15599 affects this package: high ▼ security
    • CVE-2024-55565 affects this package: high ▼ security
    • CVE-2026-41148 affects this package: high ▼ security
    • CVE-2026-41150 affects this package: high ▼ security
    • CVE-2026-65912 affects this package: high ▼ security
    • CVE-2026-50159 affects this package: high ▼ security
    • CVE-2026-65899 affects this package: high ▼ security
    • CVE-2026-66010 affects this package: high ▼ security
    • CVE-2026-71438 affects this package: high ▼ security
    • CVE-2026-65898 affects this package: high ▼ security
    • CVE-2026-65900 affects this package: high ▼ security
    • CVE-2026-41149 affects this package: high ▼ security
    • CVE-2026-41240 affects this package: high ▼ security
    • CVE-2026-71436 affects this package: high ▼ security
    • CVE-2026-49458 affects this package: high ▼ security
    • CVE-2026-49978 affects this package: high ▼ security
    • CVE-2026-67214 affects this package: high ▼ security
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/excalidraw-mcp-server@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 32 findings
ID CVE Severity Vector Fix available
GHSA-39q2-94rc-95cp CVE-2026-65903 medium yes
GHSA-55q2-fjhq-7xh7 CVE-2026-75838 medium yes
GHSA-76mc-f452-cxcm CVE-2026-65902 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-c2j3-45gr-mqc4 CVE-2026-66010 low yes
GHSA-cj63-jhhr-wcxv CVE-2026-65913 medium yes
GHSA-cjmm-f4jc-qw8r CVE-2026-65912 medium yes
GHSA-cmwh-pvxp-8882 CVE-2026-65898 medium yes
GHSA-crv5-9vww-q3g8 CVE-2026-41239 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N yes
GHSA-gvmj-g25r-r7wr CVE-2026-65900 low yes
GHSA-h7mw-gpvr-xq4m CVE-2026-41240 medium yes
GHSA-h8r8-wccr-v5f2 CVE-2026-65914 medium yes
GHSA-hpcv-96wg-7vj8 CVE-2026-49458 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-r47g-fvhr-h676 CVE-2026-49459 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-rp9w-3fw7-7cwq CVE-2026-49978 medium yes
GHSA-v2wj-7wpq-c8vv CVE-2026-0540 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-v8jm-5vwx-cfxm CVE-2025-15599 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-v9jr-rg53-9pgp CVE-2026-41238 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N yes
GHSA-vhxf-7vqr-mrjg CVE-2025-26791 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-vxr8-fq34-vvx9 CVE-2026-65899 low yes
GHSA-x4vx-rjvf-j5p4 CVE-2026-65901 low no
GHSA-2v8p-3f2j-5mp7 CVE-2026-71436 medium yes
GHSA-6m6c-36f7-fhxh CVE-2026-41150 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-6x64-9x62-f2gx CVE-2026-50159 medium yes
GHSA-87f9-hvmw-gh4p CVE-2026-41159 medium yes
GHSA-c4c3-pg64-4m4v CVE-2026-71438 low yes
GHSA-ghcm-xqfw-q4vr CVE-2026-41149 medium yes
GHSA-xcj9-5m2h-648r CVE-2026-41148 medium yes
GHSA-28wg-ghj8-5hjv CVE-2026-67214 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-2v37-7h3g-55p8 CVE-2026-67213 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mwcw-c2x4-8c55 CVE-2024-55565 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N yes
GHSA-xwg4-73v4-xw9w CVE-2026-73086 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 2
Stale 165
No linked repository 3
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~649 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
align_elements ~38

Align elements (left, center, right, top, middle, bottom)

NameTypeReqDescription
alignmentstringyes–
elementIdsarrayyes–

No output schema declared.

No examples provided.

batch_create_elements ~26

Create multiple elements at once (max 100)

NameTypeReqDescription
elementsarrayyes–

No output schema declared.

No examples provided.

create_element ~140

Create a single Excalidraw element on the canvas

NameTypeReqDescription
anglenumber––
backgroundColorstring––
fontFamilyinteger––
fontSizenumber––
groupIdsarray––
height–––
lockedboolean––
opacitynumber––
pointsarray––
roughnessnumber––
strokeColor–––
strokeWidthnumber––
textstring––
typestringyes–
widthnumber––
xnumberyes–
y–yes–

No output schema declared.

No examples provided.

create_from_mermaid ~37

Convert a Mermaid diagram to Excalidraw elements

NameTypeReqDescription
configobject––
mermaidDiagramstringyes–

No output schema declared.

No examples provided.

delete_element ~25

Delete an Excalidraw element by ID

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

distribute_elements ~32

Distribute elements evenly (horizontal or vertical)

NameTypeReqDescription
directionstringyes–
elementIdsarrayyes–

No output schema declared.

No examples provided.

export_scene ~45

Export the canvas as PNG or SVG

NameTypeReqDescription
backgroundstring––
elementIdsarray––
formatstringyes–
paddingnumber––

No output schema declared.

No examples provided.

get_resource ~26

Get scene state, elements, theme, or library

NameTypeReqDescription
resourcestringyes–

No output schema declared.

No examples provided.

group_elements ~21

Group multiple elements together

NameTypeReqDescription
elementIdsarrayyes–

No output schema declared.

No examples provided.

lock_elements ~22

Lock elements to prevent modification

NameTypeReqDescription
elementIdsarrayyes–

No output schema declared.

No examples provided.

query_elements ~43

Search for elements by type, locked status, or group ID

NameTypeReqDescription
groupIdstring––
lockedboolean––
typestring––

No output schema declared.

No examples provided.

ungroup_elements ~26

Remove elements from a group by group ID

NameTypeReqDescription
groupIdstringyes–

No output schema declared.

No examples provided.

unlock_elements ~22

Unlock elements to allow modification

NameTypeReqDescription
elementIdsarrayyes–

No output schema declared.

No examples provided.

update_element ~146

Update an existing Excalidraw element by ID

NameTypeReqDescription
anglenumber––
backgroundColorstring––
fontFamilyinteger––
fontSizenumber––
groupIdsarray––
height–––
idstringyes–
lockedboolean––
opacitynumber––
pointsarray––
roughnessnumber––
strokeColor–––
strokeWidthnumber––
textstring––
typestring––
widthnumber––
xnumber––
y–––

No output schema declared.

No examples provided.

Common questions

What is the io.github.debu-sinha/excalidraw MCP server?

io.github.debu-sinha/excalidraw is an MCP server listed in the public MCP registry as io.github.debu-sinha/excalidraw. Security-hardened Excalidraw MCP server with auth, rate limiting, and 14 tools. This page covers its npm package (excalidraw-mcp-server).

Is the io.github.debu-sinha/excalidraw MCP server safe to use?

io.github.debu-sinha/excalidraw scores 76 out of 100 on VerifyMCP. We recorded 32 known advisories against it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.debu-sinha/excalidraw MCP server expose?

io.github.debu-sinha/excalidraw exposes 14 tools: create_element, update_element, delete_element, query_elements, get_resource, and 9 more. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

Is the io.github.debu-sinha/excalidraw MCP server still maintained?

io.github.debu-sinha/excalidraw is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.debu-sinha/excalidraw MCP server under?

io.github.debu-sinha/excalidraw declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.