Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

Zebu Data - X (Twitter), YouTube & TikTok Data

MCP server · mcp.apify.com · found in a public registry · checked since 2026-10-17

Live, credentials required · latest check

As JSON

GET https://mcp.apify.com/?tools=delicious_zebu/ultimate-x-twitter-advanced-search-scraper,delicious_zebu/advanced-x-twitter-profile-scraper,delicious_zebu/x-global-trending-scraper,delicious_zebu/youtube-video-scraper-by-keyword,delicious_zebu/youtube-video-data-scraper,delicious_zebu/youtube-comments-replies-scraper,delicious_zebu/tiktok-video-comment-scraper

The name is the registry's label, not ours. Not reviewed by a person. See 571 endpoints from apify.com.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

2 passed, 0 failed, 28 not run.

Passed, 30 daysshort history2 of 2 run
Checks missed0in 30 days
Response, latest132 msto first headers
Scheduledailyset by usage; rule below
Checked since2026-10-171 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Details

Access

Our latest check
Asked for credentials (bearer token)
Stated
not stated
Payment model
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Listing

In the capability tree: Search and information / Social media / Read posts and profiles (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/4): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:MIA		 Live, MCP endpoint answered HTTP 401 132 ms

cloudflare:EWR		 Live, MCP endpoint answered HTTP 401 39 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
  • Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_465e708f507af5af