Is Zas MCP server safe?

Yes, with the usual care.

A85/100grade A

Passed every safety check we run. Maintained, authenticated, reachable, clean scan.

No critical or high findings in the latest scan.

Public scan report

scanner v0.1.6 · 2026-09-19 · same rubric, same numbers if you re-run it

1 medium

Code scan2 source files scanned20/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 1 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

mediumGoogle API key in source (often public by design; check its restrictions)secret.google

dist/cli.js: …rn process.env.ZAS_FIREBASE_API_KEY || "AIza****"; } static identityToolkitBase() { …

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

IWE
Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
not reviewed
Established
A
Agent-Native Clips
Screen recording, meeting notes, and voice dictation - all with AI
not reviewed
Established
A
Orcareplay
Read, replay and fork recorded coding-agent runs.
not reviewed
Established
A