MCP Safety Board

← All servers

MCP Safety Board · server report · November 2026

fastcrw/crw

C
70 / 100
Grade C · ★ 1,255 · Rust checked by hand

How the score was worked out

Starts at 100. Each line shows a check from the method and the points it took off.
CheckWhat was foundPoints
Risky tools labelled3 of 3 tools whose name or description suggests delete, write or run declare neither destructiveHint nor readOnlyHint. −2 each.−6
Tools with any label11 of 25 tools (44%) carry any annotation; fewer than half.−10
README install commandThe README tells users to launch the server with npx / bunx / uvx / pnpm dlx without a pinned version (or with @latest).−10
Committed config: MCP002An MCP config file committed in the repo launches a package with no version. Medium: −4 each.−4
Score100 minus the penalties above (never below 0).70

Changes that would raise this grade

  1. +10Add annotations to 2 more tools so at least half of all 25 tools are labelled (labelling the risky tools above counts too). Alone, this gives 80 (B).
  2. +10Pin the version in the README install command (pkg@1.2.3 or pkg==1.2.3, not @latest). Alone, this gives 80 (B).
  3. +6Label the 3 tools that delete, write or run: add destructiveHint (or readOnlyHint) to their annotations. Alone, this gives 76 (C).
  4. +4Pin the package version in the MCP config file committed in the repo. Alone, this gives 74 (C).

Doing all of these gives 100 (A).

What was checked

Commit checked
823c07051d7f
Repository
github.com/fastcrw/crw
Tools found
25, of which 11 carry any label (44%)
Risky tools
3, of which 0 labelled
README install
not pinned
Last push
2026-11-14

Static reading of this one commit. No code was installed or run. This is a hygiene grade, not a security audit.

Maintainer?

Fixed something, or think a count is wrong? Request a re-check (opens a GitHub issue). Re-checks run on the latest commit.

README badge

MCP safety: C
[![MCP safety: C](https://mcp-safety-board.pages.dev/badge/fastcrw--crw.svg)](https://mcp-safety-board.pages.dev/s/fastcrw--crw.html)

Want a written review of your agent's tools and permissions?

48-hour written review. Which tools your agent can call, what each one can change, which need a confirmation step, and what to lock down first. Send a message to start.