io.github.CloudCorpRecords/tokdata

tokdata

Is the io.github.CloudCorpRecords/tokdata MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-10.

TikTok public data as JSON: profile by handle, account videos, video comments, keyword search.

alive probed 2026-11-14 · unchanged since 2026-11-10

4tools

1.6ktokens in Claude Opus 5.5

0.8 %of Claude's 200k window

0.6×the median server

233 msto initialize

5 msto list tools

Run it: npx -y @reneturcios/tokdata@0.1.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: tokdata 0.1.0
Capabilities: tools
Instructions: none
Of a 1M window: 0.2 % of a 1M context window
Count: 1.6k tokens in Claude Opus 5.5, exact, measured 2026-11-10. With the Claude Code prefix mcp__…__ on each tool name: 1.6k. The o200k_base estimate is 946. Counted again when the tool definitions change. Method.
Repository: https://github.com/CloudCorpRecords/tokdata
Registry: active, updated 2026-11-10 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.68×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
hasdata_tiktok_comments_getTikTokComments	503	300	32 %
hasdata_tiktok_search_getTikTokSearch	409	244	26 %
hasdata_tiktok_posts_getTikTokPosts	404	241	25 %
hasdata_tiktok_profile_getTikTokProfile	270	161	17 %

These registry entries have the same tool names and the same schema sizes.

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention comments or account.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.