DataSocial
REMOTE · API.DATASOCIAL.AI · SCANNED OCT 5
Query a TikTok data warehouse (creators, videos, sounds, daily history) with read-only SQL.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 492 tokens (~123/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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add --transport http hashfunction-dev-datasocial-mcp 'https://api.datasocial.ai/mcp'
{
"mcpServers": {
"hashfunction-dev-datasocial-mcp": {
"url": "https://api.datasocial.ai/mcp"
}
}
} {
"servers": {
"hashfunction-dev-datasocial-mcp": {
"type": "http",
"url": "https://api.datasocial.ai/mcp"
}
}
} [mcp_servers.hashfunction-dev-datasocial-mcp] url = "https://api.datasocial.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hashfunction-dev-datasocial-mcp": {
"type": "remote",
"url": "https://api.datasocial.ai/mcp",
"enabled": true
}
}
} openclaw mcp add hashfunction-dev-datasocial-mcp --url 'https://api.datasocial.ai/mcp' --transport streamable-http
mcp_servers:
hashfunction-dev-datasocial-mcp:
url: "https://api.datasocial.ai/mcp" {
"McpServers": {
"hashfunction-dev-datasocial-mcp": {
"Transport": "http",
"Url": "https://api.datasocial.ai/mcp"
}
}
} assistant mcp add hashfunction-dev-datasocial-mcp -t streamable-http -u 'https://api.datasocial.ai/mcp'
{
"mcpServers": {
"hashfunction-dev-datasocial-mcp": {
"type": "http",
"url": "https://api.datasocial.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Sept 26 71
First indexed and scored.
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 6 Oct 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 | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5994e5987be2f80ad1d571c321516f29cba |
| 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. | present | 3799 | 8 | Verified |
| datasocial.ai. | absent | 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 |
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 →
describe_table Describe a table ~55
One table's columns with types and meanings, its sort key and coverage. Read it before writing SQL on a table.
| Name | Type | Req | Description |
|---|---|---|---|
| table | string | yes | The table, e.g. "creators" or "tiktok.creators" |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Size, grain, sort key, coverage and every column with its type and meaning |
| table | string | yes | – |
No examples provided.
examples Examples and SQL tips ~71
Worked examples (a question and SQL that runs here) and the SQL tips: growth maths, history-table patterns, big sound_history days, follows lookups. Pass a table to get only its examples.
| Name | Type | Req | Description |
|---|---|---|---|
| table | string | – | Only examples on this table, e.g. "sound_history"; omit for all |
| Name | Type | Req | Description |
|---|---|---|---|
| examples | array | yes | – |
| sql_tips | string | yes | – |
No examples provided.
list_tables 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.
| Name | Type | Req | Description |
|---|---|---|---|
| tables | array | yes | – |
No examples provided.
run_sql 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.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | One ClickHouse SELECT, e.g. SELECT username, followers FROM tiktok.creators WHERE country = 'US' ORDER BY followers DESC LIMIT 10 |
| Name | Type | Req | Description |
|---|---|---|---|
| capped | boolean | yes | true when the result was cut at the 100-row limit |
| columns | array | yes | – |
| elapsed_ms | number | yes | – |
| rows | array | yes | One array per row, values in the order of columns |
| rows_read | number | yes | – |
No examples provided.
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 74 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 244 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 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.