# Stackblade (remote · stackblade.app)

Substack writer follower counts, category leaderboards and recent rank moves.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `stackblade.app`: 74/100 (this document), [markdown](https://verifymcp.io/servers/whosman-stackblade/api-mcp.md), [page](https://verifymcp.io/servers/whosman-stackblade/api-mcp)

## Channel facts

- Endpoint: `https://stackblade.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-21.

- **Endpoint Security**: 83/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 706 tokens (~141/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Stackblade MCP server?

Stackblade is a hosted endpoint at https://stackblade.app/api/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 whosman-stackblade 'https://stackblade.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "whosman-stackblade": {
      "url": "https://stackblade.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "whosman-stackblade": {
      "type": "http",
      "url": "https://stackblade.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.whosman-stackblade]
url = "https://stackblade.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whosman-stackblade": {
      "type": "remote",
      "url": "https://stackblade.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add whosman-stackblade --url 'https://stackblade.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  whosman-stackblade:
    url: "https://stackblade.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "whosman-stackblade": {
      "Transport": "http",
      "Url": "https://stackblade.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add whosman-stackblade -t streamable-http -u 'https://stackblade.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "whosman-stackblade": {
      "type": "http",
      "url": "https://stackblade.app/api/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-21 (score 74, +6)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “board” rewrote its description, which is the text the model reads
- [security] Tool “get_writer” rewrote its description, which is the text the model reads
- [security] Tool “recent_activity” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “board” now declares an output schema
- [functional improvement] Tool “get_writer” now declares an output schema
- [functional improvement] Tool “recent_activity” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: fair → good
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “get_follow_links”
- [functional] New tool “list_categories”
- [cosmetic] “board” reworded the description of “board”
- [cosmetic] “board” reworded the description of “category”
- [cosmetic] “get_writer” reworded the description of “handle”
- [cosmetic] “recent_activity” reworded the description of “kind”

### 2026-11-20 (score 68)

First indexed and scored.

## MCP tools (5)

### `get_writer` (~162 tokens)

Get a writer

Current numbers for one Substack writer: followers, change over the last 7 and 30 days, the paid-subscriber band, current leaderboard positions and recommendation counts, with a link to the writer's page and its follower chart. Use it when someone asks how big a Substack writer or newsletter is, whether it is growing, or where it ranks. Accepts a handle, a profile link, a publication address, a custom domain or a name. When the writer is not tracked, the result says so and lists close matches.

Input parameters:

- `handle` (string, required): The writer: a Substack handle (kyla or @kyla), a profile link, a publication address such as kyla.substack.com or a custom domain, or the writer's name.

Output parameters:

- `found` (boolean)
- `guess`
- `message` (string)
- `status` (string)
- `suggestions` (array)
- `writer` (object)

### `board` (~125 tokens)

Category leaderboard

The top of one category's Substack leaderboard, with each writer's followers, paid band and move since the previous board. board is bestsellers (ranked by paid subscribers, the default) or rising (recent paid growth). category is a slug or name such as technology, business, culture or U.S. Politics; when it does not match, the result lists the closest categories.

Input parameters:

- `board` (string): bestsellers (default) or rising.
- `category` (string, required): A category slug or name, for example technology, us-politics or Food & Drink.

Output parameters:

- `board` (string)
- `category` (string)
- `rows` (array)
- `slug` (string)
- `url` (string)

### `recent_activity` (~86 tokens)

Recent activity

The latest leaderboard moves, follower milestones and new recommendations across the Substack writers Stackblade tracks, newest first, each with a link to the writer's page. kind is all (default), rank (leaderboard moves), rec (new recommendations) or followers (follower milestones). The free feed is delayed.

Input parameters:

- `kind` (string): all (default), rank, rec or followers.

Output parameters:

- `events` (array)
- `kind` (string)

### `list_categories` (~57 tokens)

List categories

Every Substack category Stackblade keeps leaderboards for, with its slug, its name and a link to its page. Each category has a bestsellers board and a rising board. Use it to find the right category for a leaderboard question.

Output parameters:

- `categories` (object)
- `count` (integer)
- `url` (string)

### `get_follow_links` (~201 tokens)

Follow or claim a writer

Links for a person who wants to keep following a Substack writer's growth, and for a writer who wants to claim their own page. Use it when the user asks to track, follow, watch or get updates on a writer (a reader, sponsor or brand), or says they are the writer. A reader gets the writer's page and a link that adds the writer to their watchlist once they confirm on the page; a writer gets a link to claim their page. Also says what the free plan and Pro include. Creates nothing: the person acts on the site.

Input parameters:

- `audience` (string): reader (default): someone who wants to follow the writer. writer: the writer, who wants to claim their page.
- `handle` (string, required): The writer: a Substack handle (kyla or @kyla), a profile link, a publication address such as kyla.substack.com or a custom domain, or the writer's name.

Output parameters:

- `audience` (string)
- `handle`
- `input` (string)
- `links` (object)
- `name`
- `plans` (object)
- `status` (string)
- `suggestions` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/whosman-stackblade/api-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 68

## Common questions

### What is the Stackblade MCP server?

Stackblade is an MCP server listed in the public MCP registry as io.github.whosman/stackblade. Substack writer follower counts, category leaderboards and recent rank moves. This page covers its hosted endpoint (https://stackblade.app/api/mcp).

### Is the Stackblade MCP server safe to use?

Stackblade 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 Stackblade MCP server expose?

Stackblade exposes 5 tools: get_writer, board, recent_activity, list_categories, get_follow_links. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.

### Does the Stackblade MCP server require authentication?

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

### Is the Stackblade MCP server still maintained?

Stackblade is still listed as active in the MCP registry. We last reached this channel on 21 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 Stackblade MCP server?

VerifyMCP ran 13 checks on Stackblade, 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://stackblade.app/api/mcp
- Repository: https://github.com/whosman/stackblade-mcp
- Website: https://stackblade.app/
- Changelog RSS feed: https://verifymcp.io/servers/whosman-stackblade/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/whosman-stackblade/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/whosman-stackblade/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/whosman-stackblade/api-mcp
