See what an MCP server lets an agent do
Lists every tool an MCP server offers and labels what each one can do: read, write, send, destructive or money. It never calls a tool, and it marks which labels come from the server and which are its own guess.
npx @stackduke/mcp-scanner scan https://huggingface.co/mcp
Review MCP tool changes before they ship
For teams that build MCP servers. The approved tool list lives in your repository, and a pull request that adds, removes or changes a tool fails until a person approves it. It runs in your own CI, and nothing is sent to Stackduke.
npx @stackduke/mcp-scanner check --update -- node dist/server.js
Set it up in CI · How check works on GitHub (opens in a new tab)
Get told when the MCP servers your agents use change
For teams whose agents use servers they did not write, such as GitHub’s, Linear’s or Stripe’s. A daily job compares each server’s tools with the list you approved, and fails, or opens an issue, when one is added, removed or changed. It is an alert, not a block.
npx @stackduke/mcp-scanner watch --update --add=https://mcp.stripe.com/
The public tool-change tracker, and what comes next
To see what official MCP servers can do and what changed, without installing anything, open Radar, our daily tracker. The scanner is MIT-licensed, and we add to it and to this page as we open-source more.