TubeSakuCREATOR DATA & SUPPORT
HomeAI data日本語 ↗

Japanese creator data.
Ready for your AI workflow.

Explore TubeSaku’s public datasets for trend research, creator discovery, and stream planning.

Explore the public data

Check generation times, observation periods, freshness, and missing values. Missing data is different from zero. Suggestion frequency is not search volume. Publication of seven-day live performance data ended when collection stopped. Source datasets may be in Japanese.

Connect your AI assistant

TubeSaku Creator Insights was registered in the official MCP Registry on October 22, 2026. Add the remote server in a compatible client. No TubeSaku login or API key is required.

Server URL
https://tubesaku.com/mcp
Transport
Streamable HTTP
Registry name
com.tubesaku/creator-insights

Read the connection guide · Plans and usage limits · Official MCP Registry

Tools cover data quality, upcoming and currently live streams, VTuber discovery, weekly game comparisons, cover-song candidates, Markdown documents, and service availability. Start with the data catalog to check coverage and freshness. The stream schedule and cover-song ranking pages also support WebMCP in compatible browsers.

Try the free preview

  • “Find three potential debut streams after 9 p.m. tonight.” Up to seven days and ten upcoming streams per MCP search.
  • “Which games are attracting attention among channels with 10,000 subscribers or fewer?” Compare demand and supply rankings for up to five games across four weeks in the free preview.
  • “Find three popular songs with fewer recent cover uploads.” Compare up to five songs, keeping original-song popularity separate from cover-upload counts.

The preview focuses on short periods and small candidate lists. Longer history, bulk access, ongoing monitoring, and custom comparisons are being considered for future paid offerings; scope and launch dates are undecided. Registered-account and paid MCP plans are Coming Soon.

Usage records

Dedicated MCP and public AI-data logs record timestamps, operations, outcomes, processing times, and HTTP status codes. MCP logs also record client names and versions, User-Agent, hashed session IDs, and identifiers linking requests. Depending on configuration, a keyed hash derived from the source IP may be recorded.

Tool names and defined arguments, such as search terms, games, dates, and result counts, are logged and aggregated to improve the service. Strings are limited to 500 characters per field. Undefined arguments, authentication headers, and raw session IDs are excluded. Search inputs can appear in logs; do not enter confidential information. Conversation text, response bodies, and raw IP addresses are not stored in these dedicated logs.

Records support service improvement, troubleshooting, and abuse prevention. Web-server and cloud-platform access logs are managed separately. For retention or deletion inquiries, contact us.

Access counts do not establish whether an AI answer cited TubeSaku or referred a user to it.