AutoSearch Channel Research Final Playbook
Date: 2026-04-19 Coverage: mcpmarket.com research + hands-on testing + TikHub paid API integration Positioning: This is the final master guide. The previously scattered docs (mcp-channel-research.md/mcp-test-plan.md/mcp-test-results.md/mcp-no-cookie-inventory.md/mcp-final-summary.md/tikhub-smoke-test.md) are consolidated here. All future channel decisions should start from this document.
TL;DR
Three-tier conclusion:- Free and usable without cookies: Sogou WeChat, open-websearch (4 engines), Paper Search MCP (21 academic sources), PullPush (Reddit history), direct RSS reads, Jina Reader (some sites), and 13 official APIs.
- 5 of 8 hard targets were unblocked through paid TikHub: Xiaohongshu, Weibo, Zhihu, Twitter/X, and Douyin. The remaining 3 (flaky Weibo upstream, Instagram/LinkedIn parameters not fully tuned) were not fully solved in this round.
- Final architecture: AutoSearch uses BYOK (users provide their own TikHub key) and declares dependencies with
requires: [env:TIKHUB_API_KEY]. The base URL is read from an env var so environments can switch cleanly.
Part 1: No-Cookie Usable Inventory (41)
A. Hands-On PASS in This Round (9)
B. Official APIs Known to Work (13, Integrated in AutoSearch or One-Line Integration)
C. New Categories Found on mcpmarket (AutoSearch Gaps) (11)
D. Existing Channel Reinforcements (8)
Part 2: Hard-Target Breakthrough Matrix
🔴 Integrated (Paid TikHub, 5/8)
⚠️ Not Fully Solved in This Round (3/8)
🟢 Truly Impossible Without Cookies
Facebook / Instagram public personal pages / Xiaohongshu private-account content / Twitter private accounts: even TikHub requires account support. These are not core to the research scenario, so do not invest for now.Part 3: TikHub Field Notes
Basic Information
- Homepage: https://tikhub.io · API base:
https://api.tikhub.io/api/v1/ - Auth:
Authorization: Bearer $TIKHUB_API_KEY - OpenAPI spec:
GET https://api.tikhub.io/openapi.json(1058 endpoints) - Billing: pay-per-request, average **0.001; measured cost is 3-4x higher)
- Free quota: Daily check-in gives a small amount of free credit
Platform Coverage (Confirmed Working)
16 platforms, 1000+ tools:Key Pitfalls (In the Order Encountered)
- Registration requires email verification. Without verification, every endpoint returns 403 “email not verified”.
- The free tier covers only some endpoints. Xiaohongshu/Weibo/Twitter/Douyin all return 402 (Payment Required) until paid balance is > 0. Zhihu and Bilibili are covered by the free tier.
- Do not use
web_v3for Xiaohongshu./xiaohongshu/web_v3/fetch_search_notesreturns 400. Use the older/xiaohongshu/web/search_notes. - Do not use
app/v3for Douyin./douyin/app/v3/fetch_video_search_resultreturns 400. Use/douyin/web/fetch_video_search_result_v2; data is underdata.business_data[i].data(two nested layers). - Weibo endpoints are unstable across versions.
web_v2/fetch_realtime_searchreturns 400;app/fetch_search_allreturns 422;web/fetch_searchreturns 200 butcardsfluctuates. - 400 = upstream scraping failure, not necessarily bad parameters. TikHub’s 400 body says “please check docs and parameters”, but in practice TikHub itself failed to scrape the target site. This kind of 400 is not billed (Only pay for successful requests).
- Twitter structure is already flattened.
data.timelineis a list, not the original GraphQL-style nestedinstructionsstructure. Iterate it directly. Fields:screen_name / text / favorites / views / retweets / replies / created_at / tweet_id / lang.
🚨 Security Note: The Key Is Echoed in Error Responses
TikHub 400 / 403 / 422 response bodies echo the full request headers, including auth information. Integration must:MCP vs API Choice
TikHub officially provides 4 transports: Stdio / SSE / Streamable HTTP / Curl(API). For AutoSearch: choose direct Curl/API calls, not MCP. Reasons:- AutoSearch is a Python plugin installed with
pip install. Using MCP would require users to additionally install Node.js +mcp-remote+ the TikHub MCP server (3 dependencies) - AutoSearch channels are already “tools”; calling MCP from inside a tool is tool-calling-a-tool, and JSON-RPC over stdio adds a useless serialization layer
- Enabling the full TikHub MCP exposes 1000+ tool schemas and injects roughly 400K tokens into Claude context, which is untenable
- Even selecting only the 6 hard-target platforms still exposes ~470 tools (~190K tokens), which is still not ideal
Part 4: Final AutoSearch Integration Architecture
BYOK (Bring Your Own Key) Is the Only Reasonable Plan
Do not:- ❌ Hardcode a TikHub key into the release build (a pip package exposes plaintext)
- ❌ Share one key across all users (violates ToS and drains the balance)
- ✅ Users register and top up at
tikhub.iothemselves - ✅
export TIKHUB_API_KEY=<your-key>, and AutoSearch reads the env var - ✅ SKILL.md declares
requires: [env:TIKHUB_API_KEY]; without a key, the channel is automatically marked unavailable while other channels continue running
Channel Structure (Validated by Pilot)
[via_tikhub, api_search, api_answer_detail] — prefer TikHub when a key is present; fall back to the original path when no key exists.
Leave Room for a Future Proxy
tikhub_client.py reads the base URL from an env var:
5 Channels Pending Integration (Priority Order)
After the pilot is validated, have Codex write the remaining 4 adapters in parallel from the same template. Each should be < 50 lines.
Appendix
A. Test Command Quick Reference (Copy-Paste Ready)
B. External Links
- mcpmarket.com — research source for this round
- tikhub.io — paid platform API
- github.com/Aas-ee/open-webSearch — 8-engine free SERP
- github.com/openags/paper-search-mcp — 21 academic sources
- github.com/jacklenzotti/pullpush-mcp — Reddit history
- r.jina.ai — free URL -> markdown via Jina Reader
C. Related Docs (Before This Round)
Consolidated into this playbook, so you no longer need to read them day to day:mcp-channel-research.md— initial researchmcp-channel-test-plan.md— test planmcp-test-results.md— first round of hands-on testsmcp-no-cookie-inventory.md— no-cookie inventorymcp-final-summary.md— phase summarytikhub-smoke-test.md— detailed TikHub smoke test
tikhub-smoke-test.md is enough.
D. Cost Ledger (As of 2026-04-19)
- TikHub: $0.053 (19 smoke requests)
- Other: $0 (all free options)
Maintenance rule: When a new channel is integrated or a new hard target is unblocked, update the corresponding table in this playbook to keep it as the single source of truth.
Appendix E. 2026-04-19 Supplemental Scan (New No-Key + No-Cookie Options)
This deeper mcpmarket.com pass found 12 fully no-key and no-cookie categories missed earlier. Ranked by research value:🔴 High Value (Strongly Recommended)
🟡 Integrate As Needed
🟢 Basic Utilities (Occasional Use)
mcpmarket Has No Coverage for These Categories
- Toutiao / Baijiahao / NetEase Hao (Chinese news aggregators)
- Reuters / TechCrunch / Bloomberg (professional news, RSS only)
- Coursera / edX / Khan Academy / MOOC
- Chinese government open data (National Bureau of Statistics, customs)
- ESPN / sports data
- Air quality / environmental data / real-time carbon emissions
site:, or by waiting for future mcpmarket additions.
2026-04-19 Hands-On Verification (5 Core MCPs)
Smoke tests were run against the underlying APIs for the 5 most important MCPs for “basic facts / trends / AI Hub / metatools.” All passed:
Key clarification: Public APIs Directory MCP (zazencodes/public-apis-mcp) does not depend on the now-dead
api.publicapis.org at all. Its data is built-in JSON (1426 entries), and the embedding index is built locally (.npz file). So even though the old API domain now fails DNS resolution, the MCP works correctly.
Pitfall warning — Google Trends: pytrends is an unofficial simulated-request library. Google occasionally changes cookie/token mechanics and breaks it. Integration must include retries + error tolerance and must not treat it as a hard dependency. It is much more fragile than the other 4 official APIs.
Integration recommendation (lightest path): The first 4 can all be called directly through Python httpx against HTTP APIs; there is no need to start an MCP process. Public APIs Directory can have its index.json copied into AutoSearch and parsed locally. A 1426-row JSON file is small, and embeddings can be computed locally. This keeps AutoSearch free of new external process dependencies.
Updated AutoSearch Priority After the Scan
On top of the 6 “strongly recommended” basics in Part 1 section C, add 3 highest-priority items:- FRED + World Bank (macroeconomic signals, no key and no cookie in one step)
- Public APIs Directory (metatool; lets AutoSearch automatically discover new channels)
- Open Library (foundation for academic/publishing research)