Skip to content
anlyon.devby Anlyon

Stackduke Radar

com.stackduke/radarstackduke.comstreamable-httpv0.1.0Scanned

Read-only answers about tool changes in the public MCP servers on Stackduke's tracker. No sign-in.

4 tools: 1 do something that can't be undone and 3 only read.

Tools: 0 delete, 1 irreversible, 0 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 1Claude Code: ask
  • get_server_capabilitiesGives 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 …Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_server_capabilities" says "get": a word for reading.
    • The description says "cannot be undone".
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.

    Findings

    • Warn

      The server marks "get_server_capabilities" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_server_capabilities" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a server's tools by kind
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • find_toolFinds which tracked vendor MCP servers list a tool with a given name, and the kind each is counted as.No findings

    Why it is in this group

    • The name "find_tool" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a tool by name
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_recent_changesGives 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…No findings

    Why it is in this group

    • The name "get_recent_changes" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get recent tool changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_tracked_serversLists the official vendor MCP servers that Stackduke's public tracker follows.No findings

    Why it is in this group

    • The name "list_tracked_servers" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List tracked MCP servers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnget_server_capabilities

    The server marks "get_server_capabilities" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_server_capabilities" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http radar https://radar.stackduke.com/mcp
claude mcp add --transport http radar https://radar.stackduke.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__radar__list_tracked_servers",
      "mcp__radar__get_recent_changes",
      "mcp__radar__find_tool"
    ],
    "ask": [
      "mcp__radar__get_server_capabilities"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as radar. Review it before you use it.

Capability tags behind 1 rule
  • mcp__radar__get_server_capabilities private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/com.stackduke/radar/verify?hash=b555b2d9a039e62ac5addc90b25e3ac4ec40a7ee3875ac2017bef8319259bdc1" | jq -e '.changed == false'

Pinned hash b555b2d9a039, from Oct 27, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.stackduke/radar/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for com.stackduke/radar
[![anlyon.dev](https://anlyon.dev/badge/com.stackduke/radar.svg)](https://anlyon.dev/servers/com.stackduke/radar)

Source: MCP Registry. Synced Oct 27, 2026, 02:17 UTC.