A
licenseNot graded
qualityF
maintenanceProvides deep, structured access to Substack publications with real-time content analysis, including sentiment analysis, readability metrics, and publishing patterns.
13
MIT
Substack Scraper MCP Server
by mambalabsdev
Related Servers
Alternatives to Substack Scraper MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables managing Substack publications: publish Notes and posts, manage drafts, pull analytics, and read any publication's public feed via MCP.MIT
- AlicenseBqualityNot gradedmaintenanceEnables interaction with Substack publications through natural conversation, allowing users to create posts with cover images, publish notes, manage content, and retrieve profile information.82 npm-
- AlicenseNot gradedqualityBmaintenanceEnables managing Substack publications through 27 tools for drafting, publishing, subscriber analytics, comments, Notes, and reader feed via Streamable HTTP.160 npm1MIT
- AlicenseBqualityDmaintenanceEnables searching, filtering, and exporting Substack blog posts via MCP tools, with full-text search, caching, and citation generation.7ISC
- FlicenseNot gradedqualityDmaintenanceEnables searching Bluesky, Substack, and Hacker News content via structured APIs with optional x402 micropayments or API key authentication.-
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation4/5
With a single tool there is no inter-tool misselection risk, and the description clearly enumerates the three modes (publication read, post read, keyword search). However, the tool internally conflates distinct operations (fetching vs. searching), and the mode is selected via a search_output parameter, which is a mild ambiguity an agent must resolve from prose.
Naming Consistency5/5
Only one tool exists, and it follows a clean verb_noun convention (scrape_substack) that matches the server name and domain. There is no mixing of conventions to penalize.
Tool Count3/5
A single tool for a domain that spans publication lookup, post retrieval, and keyword search is thin, and the overloaded parameter surface suggests it could reasonably be split into fetch_publication, fetch_posts, and search_posts. It is not egregiously wrong, but the count is borderline for the described scope.
Completeness3/5
Read-only coverage of publications, posts, and search is reasonable for a scraper, but there are notable gaps: no way to fetch an arbitrary post by URL, no comments retrieval despite comments being reported, and no explicit pagination/limit controls. Agents hitting those needs will dead-end.
Maintenance
ActivityMaintained
ResponsivenessNo issues