MCP Safety Board

← All servers

MCP Safety Board · server report · November 2026

cjo4m06/mcp-shrimp-task-manager

B
84 / 100
Grade B · ★ 2,151 · JavaScript 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 label0 of 15 tools (0%) carry any annotation; fewer than half.−10
README install commandThe README has no npx / bunx / uvx / pnpm dlx launch command, so there is nothing to pin.0
Committed configNo committed MCP config with an unpinned package, a moving tag, a broad filesystem root, a privileged docker server or plain http.0
Score100 minus the penalties above (never below 0).84
  • MCP106 (1): A destructive tool has no annotations (recorded only: already counted in the tool-label check). No points.

Changes that would raise this grade

  1. +10Add annotations to 8 more tools so at least half of all 15 tools are labelled (labelling the risky tools above counts too). Alone, this gives 94 (A).
  2. +6Label the 3 tools that delete, write or run: add destructiveHint (or readOnlyHint) to their annotations. Alone, this gives 90 (A).

Doing all of these gives 100 (A).

What was checked

Commit checked
8a3be6bced31
Repository
github.com/cjo4m06/mcp-shrimp-task-manager
Tools found
15, of which 0 carry any label (0%)
Risky tools
3, of which 0 labelled
README install
no npx/uvx snippet
Last push
2025-08-21

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: B
[![MCP safety: B](https://mcp-safety-board.pages.dev/badge/cjo4m06--mcp-shrimp-task-manager.svg)](https://mcp-safety-board.pages.dev/s/cjo4m06--mcp-shrimp-task-manager.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.