MCP Safety Board · server report · November 2026
dondai1234/master-fetch
A
100 / 100
Grade A · ★ 903 · Python checked by hand
How the score was worked out
| Check | What was found | Points |
|---|---|---|
| Risky tools labelled | All 1 tools that look like they delete, write or run things declare destructiveHint or readOnlyHint. | 0 |
| Tools with any label | 6 of 6 tools (100%) carry any annotation; half or more. | 0 |
| README install command | The README has no npx / bunx / uvx / pnpm dlx launch command, so there is nothing to pin. | 0 |
| Committed config | No committed MCP config with an unpinned package, a moving tag, a broad filesystem root, a privileged docker server or plain http. | 0 |
| Score | 100 minus the penalties above (never below 0). | 100 |
Changes that would raise this grade
Nothing to change: this server already gets full marks on every check.
What was checked
- Commit checked
86d1b1329c0e- Repository
- github.com/dondai1234/master-fetch
- Tools found
- 6, of which 6 carry any label (100%)
- Risky tools
- 1, of which 1 labelled
- README install
- no npx/uvx snippet
- Last push
- 2026-07-24
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
[](https://mcp-safety-board.pages.dev/s/dondai1234--master-fetch.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.