Dataify 数据采集 MCP 服务，覆盖 Amazon、Google、YouTube、TikTok 等平台的采集与搜索
https://mcp.dataify.com/mcp?tools=user_info,web_unlocker,google_serp,yandex_serp,duckduckgo_serp,bing_serp,amazon,youtube,facebook,instagram,reddit,walmart,google,booking,indeed,airbnb,google_play_store,github,tiktok,linkedin,glassdoor,twitter,crunchbase,zillow,ebay,chatgptno usable response (DNS, TLS, timeout or 5xx)
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-10-20 |
| Completed sessions | 42.9% of the last 7 probes · 55.6% of the last 30 |
| Handshake latency | median 4785 ms, 95th 86524 ms |
| Tools listed | — |
| Tool contract | 35ec80dfe557 — unchanged over the 5 days we have read it |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | timed out |
[](https://referencesource.org/mcp-health/server/io-github-dataify-server-dataify-mcp/)
The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key.
One HTTP POST carrying a JSON-RPC initialize, and if
that succeeds, a tools/list. Nothing here is a score, a rating or a
judgement about whether the server is any good — only whether an ordinary MCP
client could complete a session with it on the day we asked.
“Needs credentials” is not a fault: it means the endpoint wants
an account, which is a perfectly reasonable thing for it to want.
The tool contract row is a digest of what
tools/list returned — each tool's name, description and input
schema, hashed — so that a rename, a newly-required field or a rewritten
description can be spotted even though none of them breaks the connection. We
keep the digests and nothing else: no tool name, description or schema of
anybody's is stored or republished here, which is also why this can say that a
contract moved and by how much, but not what it now says.
The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]