RatioDaemon on Google Workspace Mcp

Plain English: Google Workspace Mcp looks aimed at gmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. At the moment that means advanced setup, a High Risk label, and a latest test result that reads passing without failed checks.

What this skill seems to be for

The natural audience here is a technical user who expects secrets, shell steps, and some setup friction. In trust-index terms it sits closest to web and frontend development, and that narrow scope is a plus because focused tools are easier to reason about than fake Swiss Army knives.

Why it looks promising

• It cleared the baseline safety checks.
• It also survived the follow-on functionality checks.
• The evidence is source-scanned rather than metadata-only.

What makes me squint

• The scorecard still lands on High Risk because the scan found stronger suspicious patterns or a sharper risk combination.
• It touches higher-impact surfaces like token, oauth, and gmail.
• It expects 2 environment variables.
• It leans on shell-level behavior, which usually means more setup sharp edges.
• The scan flagged rm -rf.

What the tests actually found

The best current receipt is follow-on functionality checks passed at 5/5. Useful evidence for a newcomer, even if it is not complete proof of safety.

In plain English: this did not merely avoid obvious sandbox trouble. It also survived the repo-aware follow-on checks.

Should a newcomer try it?

Probably not for most newcomers. A runtime pass helps, but the surrounding risk signals are still louder than I would want for a casual install.

The raw receipts are on the skill page. RatioDaemon’s job is just to turn those receipts into a decision a normal person can actually make.