Stackduke Radar MCP Server

by stackduke Your server? Claim it

answering

Stackduke Radar is answering right now. Last checked 13 min ago. It exposes 4 tools.

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

Uptime history 8 days of history

8 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

134 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Stackduke Radar every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://radar.stackduke.com/mcp

~/.codex/config.toml

[mcp_servers.radar]
url = "https://radar.stackduke.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "radar": {
      "url": "https://radar.stackduke.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "radar": {
      "type": "http",
      "url": "https://radar.stackduke.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

recent

get_recent_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.

server

get_server_capabilities

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.

tool

find_tool

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.

tracked

list_tracked_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.

Endpoints

URL	Transport	State	Latency	Checked
https://radar.stackduke.com/mcp	streamable-http	answering	186 ms	13 min ago

Alternatives to Stackduke Radar

same job, measured the same way

MCP Abap Adt Compact Ro

by fr0ster

Read-only compact MCP server for SAP ABAP ADT: the compact tools that change nothing

1 151 installs/wk local only

MCP Checkup

by mcpcheckup

Observed facts on public MCP servers: protocol checks, tool changes, signed evidence. No verdicts.

6 tools answering

Chia Explorer

by spacetime-technology

MCP server for the Chia blockchain. Read-only Q&A via the public coinset.org API.

110 installs/wk local only

Vargov®Design

by vargov

Read-only MCP server with Vargov®Design public data: compositions, answers, configurator, dealers.

5 tools answering

Krobot

by kromatic-innovation

Kromatic's public MCP server for read-only access to the Kromatic knowledge base.

answering

Bostrom MCP

by cyberia-to

86-tool MCP server for Bostrom blockchain: read chain state and sign transactions

160 installs/wk local only

AgentScout

by agentscouthq

Read-only search over 2,065+ AI agent tools and 276 MCP servers. Free, no sign-up needed.

5 tools answering

Remember Me – Bible Verse Collections

by remem

Browse Bible verse collections to memorize, in 48 languages. Public and read-only, no sign-in.

3 tools answering

Stackduke Radar — questions

Answers built from our own checks of this server.

What can Stackduke Radar do?

It exposes 4 tools, read directly from the server on our last check. Among them: find_tool, get_recent_changes, get_server_capabilities, list_tracked_servers. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Stackduke Radar working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 134 ms. The bar chart above shows every period we have measured.

How do I connect Stackduke Radar?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Stackduke Radar need an API key?

No. Stackduke Radar completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Stackduke Radar?

It answers our handshake in 134 ms on average, which is faster than 88% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.