Is tabnas MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
What to know before installing
- highWrite-action tools reachable without authentication
How tabnas compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools that change things
- 14%
- 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: 6 read · 1 change
Release history: 4 versions in the registry since 2026-08-22, latest 2026-10-08, typically one every 10 days.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
1 high
- Code scan32 source files scanned25/25
- Live reliabilityremote reachable in 283ms20/20
- Tool poisoning7 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 24 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON