excalidrop@0.2.7
Remote GitHub-backed Excalidraw canvas + MCP server — no local server, one-command setup
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe relay supports the package’s remote canvas features, and its use is documented, but the MCP server also sends a GitHub credential to that relay by default for screenshot and viewport requests. That creates a meaningful credential exposure risk, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The MCP server reads GitHub credentials from GITHUB_TOKEN, gh auth, or its stored token file.
- Relay requests send the resolved GitHub token as a Bearer credential to the default Excalidrop relay host.
- The relay is used for user-triggered screenshot and viewport operations.
- The README identifies the shared relay, but does not explain that GitHub credentials are sent to it.
- The package is described as a remote GitHub-backed canvas, and relay operations serve that feature.
- GitHub login uses GitHub’s device flow, and the relay calls occur when screenshot or viewport operations are requested.
- The README discloses that screenshots and viewport features use the shared relay.
Source & flagged code
9 flaggedPackage contains a high-severity secret pattern.
dist/frontend/assets/index-DPE4WCka.jsView on unpkg · L41Google API key in dist/frontend/assets/index-DPE4WCka.js
dist/frontend/assets/index-DPE4WCka.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to excalidrop@0.2.7.
See all versions of excalidrop for other recorded verdicts.
- Review the evidence and your use of excalidrop@0.2.7 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.