MCP Safety Board · server report · November 2026
akfamily/aktools
A
90 / 100
Grade A · ★ 1,566 · Python checked by hand
How the score was worked out
| Check | What was found | Points |
|---|---|---|
| Risky tools labelled | No tool name or description suggests delete, remove, drop, write, update, run, execute, eval, kill or revoke. | 0 |
| Tools with any label | 3 of 3 tools (100%) carry any annotation; half or more. | 0 |
| README install command | The README tells users to launch the server with npx / bunx / uvx / pnpm dlx without a pinned version (or with @latest). | −10 |
| 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). | 90 |
Changes that would raise this grade
- +10Pin the version in the README install command (pkg@1.2.3 or pkg==1.2.3, not @latest). Alone, this gives 100 (A).
What was checked
- Commit checked
b6b77bd35eee- Repository
- github.com/akfamily/aktools
- Tools found
- 3, of which 3 carry any label (100%)
- Risky tools
- 0
- 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
[](https://mcp-safety-board.pages.dev/s/akfamily--aktools.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.