Is Canvasaas MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How Canvasaas compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
What its tools let an agent do: 2 read
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
1 medium
- Code scan19 source files scanned20/25
- Live reliabilityremote reachable in 1940ms20/20
- Tool poisoning2 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 58 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumHeavily hex-escaped string (obfuscation)
obf.hex-densitydist/api.js: …34a6af,'\x68\x65\x61\x64\x65\x72\x73':{'\x43\x6f\x6e\x74\x65\x6e\x74\x2d\x54\x79\x70\x65':_0x11180a[_0xdd27a9(0x3f8,'\x34\x4a\x2…
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON