com.stackdukePublished by stackduke.comOfficial publisherv0.1.0Updated Oct 29, 2026
Read-only answers about tool changes in the public MCP servers on Stackduke's tracker. No sign-in.
Read-only remote MCP server that answers questions about the tool lists and recent tool changes of vendor MCP servers tracked by Stackduke Radar.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.stackduke%2Fradar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"stackduke-radar": {
"type": "http",
"url": "https://radar.stackduke.com/mcp"
}
}
}List tracked MCP servers
Lists the official vendor MCP servers that Stackduke's public tracker follows. For each: its tool count, its tools counted by kind (money, destructive, send, write, unclear, read), when it was last checked and when its tools were last listed. Only these servers are covered. The tracker data is published about once a day. Read-only: answers come from Stackduke's published tracker data, and no vendor's server is contacted.
Takes no parameters.
Get a server's tools by kind
Gives the tool names on one tracked vendor MCP server, grouped by the most serious thing each tool is counted as able to do: money (move or spend money), destructive (changes that cannot be undone, such as deleting), send (send messages or publish to other people), write (create or change things), unclear, or read (labelled as only reading). Labels come from Stackduke's open-source scanner: the server's own annotations where it sends them, otherwise a guess from the tool's name that leans to the more serious kind. They are not verified by calling the tools, and they do not mean a server is safe. Tool descriptions are never included. A server the tracker does not follow gets a 'not covered' answer.
kindvendorrequiredGet recent tool changes
Gives the changes seen to one tracked vendor MCP server's tool list in the last 1 to 30 days (default 7): tools added and removed, tools changed with the fields that changed (title, description, input or output schema, annotations), and tools now counted as able to do more than before. Each change is dated as seen between two checks, because the tracker compares one listing with the next. The answer also says how many checks were made in the period, which ones failed, and any stretch that was not watched. A change made and undone between two checks is not seen. Changed text is never quoted. A server the tracker does not follow gets a 'not covered' answer.
daysvendorrequiredFind a tool by name
Finds which tracked vendor MCP servers list a tool with a given name, and the kind each is counted as. By default it matches the whole name, ignoring case; with match set to 'contains' it finds names containing the text (at least 3 characters). Searches only the servers the tracker follows, at their latest listing.
namerequiredmatch83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.