TikHub vs FeedMCP: Raw scraper endpoints vs unified AI schema & hosted MCP server
TikHub is a capable raw scraper aggregator, but exposes multiple overlapping Web/App versions per platform with deeply nested raw JSON, and lacks WeChat Index, Meta/Google/LinkedIn Ad Libraries or a lightweight 4-tool remote MCP. FeedMCP combines four upstreams (TikHub, ScrapeCreators, TwitterAPI.io and Jizhile) into one normalized JSON schema across 21 platforms, with hosted MCP, X-Max-Price guardrails and failed-call protection.
Side-by-side comparison
| Criteria | FeedMCP (Unified AI Data Layer + MCP) | TikHub (Raw Scraper Aggregator) |
|---|---|---|
| Upstream coverage | Combines 4 upstreams: China social + WeChat Index + global social + 4 Ad Libraries + TikTok Shop + transcripts | Single provider: raw social endpoints; no WeChat Index or Meta/Google/LinkedIn Ad Libraries |
| Response JSON shape | Unified schema across all 21 platforms (compact, predictable fields; saves >85% LLM tokens) | Raw internal App/Web payloads (hundreds of deeply nested fields that bloat LLM context) |
| Endpoint curation | 1 canonical, live-verified endpoint per action (193 total) | Hundreds of overlapping Web/App V1/V2/V3 variants per platform requiring manual trial and error |
| MCP & Agent UX | Hosted https://api.feedmcp.com/mcp with 4 compact tools (find, describe, call, account) |
Exposing hundreds of raw endpoints directly overwhelms agent tool limits |
| Spend safety | X-Max-Price ceiling + 24h Idempotency-Key replay + per-key budget caps |
No per-call price cap header or built-in 24h idempotent replay |
When FeedMCP is the right fit
- You want Claude, Cursor or your backend to query 21 platforms with one parser instead of maintaining 21 platform-specific JSON normalizers
- You need WeChat Index, Meta/Google/LinkedIn Ad Libraries, AI video transcripts or $0.0003/item X threads under the same API key
When another option makes more sense
- You need obscure platform-internal protocol fields (note: FeedMCP also supports
view=fullon reviewed endpoints to include extra platform business fields)
Next steps
Questions
TikHub vs FeedMCP: Raw scraper endpoints vs unified AI schema & hosted MCP server
TikHub is a capable raw scraper aggregator, but exposes multiple overlapping Web/App versions per platform with deeply nested raw JSON, and lacks WeChat Index, Meta/Google/LinkedIn Ad Libraries or a lightweight 4-tool remote MCP. FeedMCP combines four upstreams (TikHub, ScrapeCreators, TwitterAPI.io and Jizhile) into one normalized JSON schema across 21 platforms, with hosted MCP, X-Max-Price guardrails and failed-call protection.
Can I test FeedMCP data quality before paying?
Yes. Sign up in the console with your email for $0.10 free trial credit (no card)—enough for 50 calls to $0.002 endpoints or 5 calls to $0.02 endpoints.
More comparisons
- Best social media data APIs & MCP servers (2026): FeedMCP vs DataXAPI vs Qovia vs AIsa vs TikHub
- Social media MCP servers compared: FeedMCP vs browser MCP vs local scraper MCP
- Xiaohongshu (RedNote) data API options compared: Official vs Scrapers vs SaaS vs FeedMCP
- WeChat Official Account API comparison: Official MP vs wewe-rss vs SaaS vs FeedMCP
- Douyin & TikTok data API comparison: Official Research API vs Scrapers vs FeedMCP
- X (Twitter) API pricing compared: Official $200/mo Basic vs FeedMCP pay-per-call
- MCP vs REST API for social media data: which one should you use?