MCP Safety Board

← All servers

MCP Safety Board · server report · November 2026

OpenOSINT/OpenOSINT

C
78 / 100
Grade C · ★ 1,934 · Python 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 labelled1 of 1 tools whose name or description suggests delete, write or run declares neither destructiveHint nor readOnlyHint. −2 each.−2
Tools with any label0 of 25 tools (0%) 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 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).78

Changes that would raise this grade

  1. +10Add annotations to 13 more tools so at least half of all 25 tools are labelled (labelling the risky tools above counts too). Alone, this gives 88 (B).
  2. +10Pin the version in the README install command (pkg@1.2.3 or pkg==1.2.3, not @latest). Alone, this gives 88 (B).
  3. +2Label the 1 tool that deletes, writes or runs: add destructiveHint (or readOnlyHint) to its annotations. Alone, this gives 80 (B).

Doing all of these gives 100 (A).

What was checked

Commit checked
8b7b51fbf39e
Repository
github.com/OpenOSINT/OpenOSINT
Tools found
25, of which 0 carry any label (0%)
Risky tools
1, 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/openosint--openosint.svg)](https://mcp-safety-board.pages.dev/s/openosint--openosint.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.