read-post-mcp
Related Servers
Alternatives to read-post-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceTurns TikTok, Instagram, X/Twitter and Facebook post URLs into video download links plus metadata (title, author, duration, thumbnail), so AI agents can fetch social videos in one tool call.364 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve X/Twitter profiles and tweets, YouTube video and channel data, and TikTok profile and video stats on a pay-per-result basis without requiring login or platform API keys.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to read one public X/Twitter post from a status URL without cookies, returning post text, quoted content, links, and media URLs as untrusted data.MIT
- AlicenseAqualityDmaintenanceProvides AI agents with unified access to 21 social media platforms and 105 endpoints for retrieving profiles, posts, comments, search results, trending content, and analytics without per-platform authentication.4132 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read social media and article links that return no useful HTML, returning transcripts, on-screen text, image OCR, captions, metadata, and optional viral breakdowns with verbatim-checked quotes or translations. Works with Xiaohongshu, Douyin, TikTok, YouTube, X, and ordinary web pages through a hosted remote endpoint, with a Python SDK, CLI, and stdio bridge for clients that need them.2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read data from Instagram, TikTok, YouTube, App Store, GitHub, Hacker News, Bluesky, Twitch, and Linktree through the ScrapingIsNotACrime public API.345 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlap with a sibling tool. Its purpose is stated unambiguously in both name and description.
The single tool uses a clear snake_case verb_noun name (read_post) that matches the server name and the operation it performs. There are no competing conventions to conflict with.
A one-tool surface is thin by the general rubric, but the server's stated scope is exactly one operation (fetch and parse a post from a URL), so nothing extra is padding. It sits at the borderline rather than being mismatched.
For a read-only fetch-a-post domain, the tool covers the full expected payload: text, author, date, stats, links, media, and video, with explicit limits (no private posts) and a broad platform list. No batch/multi-URL variant or structured error/fallback operation, but the core lifecycle is complete.