Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DataSocial

REMOTE · API.DATASOCIAL.AI

Query a TikTok data warehouse (creators, videos, sounds, daily history) with read-only SQL.

0 this week 84 Trust /100

Last scanned (19 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security71
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 473 tokens (~118/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “examples” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.datasocial.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=datasocial.ai CN=YE2,O=Let's Encrypt,C=US 18 Nov 2026 16 Feb 2027 ECDSA 256 ECDSA-SHA384 51dfce694ddebc74b8b19a73f8ec1f27c0a
SANs: *.datasocial.ai, datasocial.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.datasocial.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
datasocial.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.datasocial.ai/mcp Verified 200
http (plaintext) http://api.datasocial.ai/mcp Inconclusive 405
MCP tools · 4 exposed · ~240 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
describe_table ~55

One table's columns with types and meanings, its sort key and coverage. Read it before writing SQL on a table.

NameTypeReqDescription
tablestringyesThe table, e.g. "creators" or "tiktok.creators"
NameTypeReqDescription
descriptionstringyesSize, grain, sort key, coverage and every column with its type and meaning
tablestringyes–

No examples provided.

examples ~67

Worked examples (a question and SQL that runs here) and the SQL tips: growth maths, history-table patterns, big sound_history days. Pass a table to get only its examples.

NameTypeReqDescription
tablestring–Only examples on this table, e.g. "sound_history"; omit for all
NameTypeReqDescription
examplesarrayyes–
sql_tipsstringyes–

No examples provided.

list_tables ~33

The tables in the DataSocial TikTok warehouse: name, row count, what one row is, and what it holds.

Input schema present but exposes no named parameters.

NameTypeReqDescription
tablesarrayyes–

No examples provided.

run_sql ~85

Run one read-only ClickHouse SELECT on tiktok.* and get the rows back (at most 100 per request; 10 s per query). Name the columns you need and add a LIMIT.

NameTypeReqDescription
sqlstringyesOne ClickHouse SELECT, e.g. SELECT username, followers FROM tiktok.creators WHERE country = 'US' ORDER BY followers DESC LIMIT 10
NameTypeReqDescription
cappedbooleanyestrue when the result was cut at the 100-row limit
columnsarrayyes–
elapsed_msnumberyes–
rowsarrayyesOne array per row, values in the order of columns
rows_readnumberyes–

No examples provided.

Install

How do I install the DataSocial MCP server?

DataSocial is a hosted endpoint at https://api.datasocial.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.datasocial.ai

# add to Claude Code
claude mcp add --transport http hashfunction-dev-datasocial-mcp 'https://api.datasocial.ai/mcp'
Common questions

What is the DataSocial MCP server?

DataSocial is an MCP server listed in the public MCP registry as io.github.hashfunction-dev/datasocial-mcp. Query a TikTok data warehouse (creators, videos, sounds, daily history) with read-only SQL. This page covers its hosted endpoint (https://api.datasocial.ai/mcp).

Is the DataSocial MCP server safe to use?

DataSocial scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DataSocial MCP server expose?

DataSocial exposes 4 tools: list_tables, describe_table, examples, run_sql. Their descriptions and schemas cost roughly 240 tokens of context every time the server is loaded.

Does the DataSocial MCP server require authentication?

Yes. DataSocial asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the DataSocial MCP server still maintained?

DataSocial is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the DataSocial MCP server?

VerifyMCP ran 12 checks on DataSocial, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about DataSocial: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.