Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Stackblade

REMOTE · STACKBLADE.APP

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

Available components

74 Trust /100

Last scanned (22 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +6
    • 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 security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “board” now declares an output schema ▲ functional
    • Tool “get_writer” now declares an output schema ▲ functional
    • 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” functional
    • “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” cosmetic
  • 20 Nov 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://stackblade.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=stackblade.app CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 bdd19ec84afafe0913cf978f119adb41
SANs: stackblade.app, www.stackblade.app, *.www.stackblade.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of stackblade.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
stackblade.app. DS published 2371 13 Verified
stackblade.app. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stackblade.app/api/mcp Verified 200
http (plaintext) http://stackblade.app/api/mcp HTTPS enforced 301 https://stackblade.app/api/mcp
MCP tools · 5 exposed · ~631 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
board ~125

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.

NameTypeReqDescription
boardstring–bestsellers (default) or rising.
categorystringyesA category slug or name, for example technology, us-politics or Food & Drink.
NameTypeReqDescription
boardstringyes–
categorystringyes–
rowsarrayyes–
slugstring––
urlstringyes–

No examples provided.

get_follow_links ~201

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.

NameTypeReqDescription
audiencestring–reader (default): someone who wants to follow the writer. writer: the writer, who wants to claim their page.
handlestringyesThe 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.
NameTypeReqDescription
audiencestringyes–
handle–––
inputstringyes–
linksobjectyes–
name–––
plansobject––
statusstringyes–
suggestionsarrayyes–

No examples provided.

get_writer ~162

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.

NameTypeReqDescription
handlestringyesThe 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.
NameTypeReqDescription
foundbooleanyes–
guess–––
messagestring––
statusstringyes–
suggestionsarrayyes–
writerobject––

No examples provided.

list_categories ~57

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesobjectyes–
countintegeryes–
urlstringyes–

No examples provided.

recent_activity ~86

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.

NameTypeReqDescription
kindstring–all (default), rank, rec or followers.
NameTypeReqDescription
eventsarrayyes–
kindstringyes–

No examples provided.

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.

remote · stackblade.app

# add to Claude Code
claude mcp add --transport http whosman-stackblade 'https://stackblade.app/api/mcp'
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.