MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Substack MCP Server

Earlier Revision Publisher unverified Confidence: Good (0.85)

Substack MCP Server is an MCP server published by conorbronsdon, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does Substack MCP Server support the current MCP specification (2026-07-28)?

Not yet confirmed. Substack MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is Substack MCP Server a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for Substack MCP Server (as of 2026-08-20).

How do I connect to Substack MCP Server?

Substack MCP Server is available via the package npm:@conorbronsdon/substack-mcp, the official MCP Registry under io.github.conorbronsdon/substack-mcp, the source repository at https://github.com/conorbronsdon/substack-mcp. Authentication: unknown. Transports: stdio.

Does Substack MCP Server support MCP revision 2025-11-25?

Yes. Substack MCP Server supports MCP revision 2025-11-25 (checked 2026-08-20).

Does Substack MCP Server support MCP revision 2026-07-28?

No. Substack MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were Substack MCP Server's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

Substack MCP server: posts are draft-only by design; short-form Notes publish immediately.

Which MCP spec revisions does Substack MCP Server support?

Substack MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is Substack MCP Server?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for Substack MCP Server

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Stars
20
Forks
6
Last pushed
(57 days ago)
Created
Open issues
1
Primary language
TypeScript
License (repository)
MIT
Continuous integration
Present
Tests
None detected
Security policy
Present

Declared topics: ai-agents, claude, claude-code, content-creation, developer-tools, mcp, mcp-server, model-context-protocol, substack, typescript — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
0.6.2
Last published
First published
Releases
9
License (package)
MIT
Maintainers
1
Direct dependencies
2
Unpacked size
260 KB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.conorbronsdon/substack-mcp at version 0.6.2 - lists package npm:@conorbronsdon/substack-mcp and repository https://github.com/conorbronsdon/substack-mcp - accessed
  2. npm registry metadata for @conorbronsdon/substack-mcp at published version 0.6.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed