# Stackduke Radar (remote · radar.stackduke.com)

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

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `radar.stackduke.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-stackduke-radar/radar.md), [page](https://verifymcp.io/servers/com-stackduke-radar/radar)

## Channel facts

- Endpoint: `https://radar.stackduke.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 681 tokens (~170/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Stackduke Radar MCP server?

Stackduke Radar is a hosted endpoint at https://radar.stackduke.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-stackduke-radar": {
      "type": "remote",
      "url": "https://radar.stackduke.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-stackduke-radar --url 'https://radar.stackduke.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-stackduke-radar:
    url: "https://radar.stackduke.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-stackduke-radar": {
      "Transport": "http",
      "Url": "https://radar.stackduke.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-stackduke-radar -t streamable-http -u 'https://radar.stackduke.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-stackduke-radar": {
      "type": "http",
      "url": "https://radar.stackduke.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 69)

First indexed and scored.

## MCP tools (4)

### `list_tracked_servers` (~101 tokens)

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.

Output parameters:

- `data_as_of` (string): When the tracker data was published.
- `servers` (array)
- `source` (string): The tracker page this answer is drawn from.
- `summary` (string)

### `get_server_capabilities` (~203 tokens)

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.

Input parameters:

- `kind` (string): Optional. Only the tools counted as this kind.
- `vendor` (string, required): The server, by id or name, for example "huggingface" or "Microsoft Learn".

Output parameters:

- `covered` (boolean)
- `covered_vendors` (array)
- `data_as_of` (string): When the tracker data was published.
- `groups` (array)
- `last_listed` (string|null)
- `name` (string)
- `names_withheld` (integer)
- `source` (string): The tracker page this answer is drawn from.
- `summary` (string)
- `tool_count` (integer|null)
- `vendor` (string)
- `vendor_asked` (string)

### `get_recent_changes` (~199 tokens)

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

Input parameters:

- `days` (integer): How many days back to look, 1 to 30. Default 7.
- `vendor` (string, required): The server, by id or name, for example "huggingface" or "Microsoft Learn".

Output parameters:

- `changes` (array)
- `checks_in_period` (integer)
- `covered` (boolean)
- `covered_vendors` (array)
- `data_as_of` (string): When the tracker data was published.
- `days` (integer)
- `failed_checks` (array)
- `failed_checks_total` (integer)
- `last_listed` (string|null)
- `listings_in_period` (integer)
- `name` (string)
- `older_changes_may_be_missing` (boolean)
- `period` (object)
- `source` (string): The tracker page this answer is drawn from.
- `summary` (string)
- `unwatched_stretches` (array)
- `vendor` (string)
- `vendor_asked` (string)
- `watched_from` (string|null)

### `find_tool` (~97 tokens)

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

Input parameters:

- `match` (string)
- `name` (string, required): A tool name, for example "delete_issue".

Output parameters:

- `data_as_of` (string): When the tracker data was published.
- `match` (string)
- `matches` (array)
- `query` (string)
- `servers_searched` (array)
- `source` (string): The tracker page this answer is drawn from.
- `summary` (string)
- `total_matches` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-stackduke-radar/radar#diagnostics

## Score history

- 2026-11-06: 74
- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69

## Common questions

### What is the Stackduke Radar MCP server?

Stackduke Radar is an MCP server listed in the public MCP registry as com.stackduke/radar. Read-only answers about tool changes in the public MCP servers on Stackduke's tracker. No sign-in. This page covers its hosted endpoint (https://radar.stackduke.com/mcp).

### Is the Stackduke Radar MCP server safe to use?

Stackduke Radar scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Stackduke Radar MCP server expose?

Stackduke Radar exposes 4 tools: list_tracked_servers, get_server_capabilities, get_recent_changes, find_tool. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.

### Does the Stackduke Radar MCP server require authentication?

No. We connected to Stackduke Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Stackduke Radar MCP server still maintained?

Stackduke Radar is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Stackduke Radar MCP server?

VerifyMCP ran 13 checks on Stackduke Radar, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://radar.stackduke.com/mcp
- Website: https://stackduke.com/tracker
- Changelog RSS feed: https://verifymcp.io/servers/com-stackduke-radar/radar.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-stackduke-radar/radar/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-stackduke-radar/radar.json
- HTML version of this page: https://verifymcp.io/servers/com-stackduke-radar/radar