Fetchwire - Social Data
REMOTE · MCP.FETCHWIRE.DEV · SCANNED SEP 20
YouTube, TikTok, Instagram, X, Reddit, LinkedIn and Threads: public data in one schema.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1511 tokens (~151/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Fetchwire - Social Data MCP server?
Fetchwire - Social Data is a hosted endpoint at https://mcp.fetchwire.dev/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 · mcp.fetchwire.dev
claude mcp add --transport http dev-fetchwire-social-data 'https://mcp.fetchwire.dev/mcp'
{
"mcpServers": {
"dev-fetchwire-social-data": {
"url": "https://mcp.fetchwire.dev/mcp"
}
}
} {
"servers": {
"dev-fetchwire-social-data": {
"type": "http",
"url": "https://mcp.fetchwire.dev/mcp"
}
}
} [mcp_servers.dev-fetchwire-social-data] url = "https://mcp.fetchwire.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-fetchwire-social-data": {
"type": "remote",
"url": "https://mcp.fetchwire.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-fetchwire-social-data --url 'https://mcp.fetchwire.dev/mcp' --transport streamable-http
mcp_servers:
dev-fetchwire-social-data:
url: "https://mcp.fetchwire.dev/mcp" {
"McpServers": {
"dev-fetchwire-social-data": {
"Transport": "http",
"Url": "https://mcp.fetchwire.dev/mcp"
}
}
} assistant mcp add dev-fetchwire-social-data -t streamable-http -u 'https://mcp.fetchwire.dev/mcp'
{
"mcpServers": {
"dev-fetchwire-social-data": {
"type": "http",
"url": "https://mcp.fetchwire.dev/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.
- 20 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 62
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 20 Sept 2026 · Probed https://mcp.fetchwire.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fetchwire.dev | CN=WR3,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | RSA 2048 | SHA256-RSA | d33df1fe9acbbe000a36ae88e3728988 |
| SANs: fetchwire.dev, api.fetchwire.dev, mcp.fetchwire.dev | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.fetchwire.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fetchwire.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.fetchwire.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.fetchwire.dev/mcp | HTTPS enforced | 301 | https://mcp.fetchwire.dev/mcp |
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 →
call_route Call any route ~84
Fetch any Fetchwire route by path, for the routes the operation tools do not cover. Find the path with list_routes first. `params` are the query parameters, e.g. call_route('/v1/tiktok/hashtag/videos', {'id': 'space'}). Spends credits like any other call.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
get_comments Get comments on a post ~235
Comments on a post, flat, with `parent_id` set on replies so the tree is one pass to rebuild. A comment's `replies_cursor` passed as `cursor` returns that thread. instagram: username or profile URL; for posts, a shortcode or /p/ or /reel/ URL. linkedin: profile slug or /in/ URL; for posts, an activity id or /posts/ URL. reddit: username, u/name, or profile URL; for posts, a t3_ id, bare id, or comments URL. threads: username, numeric user id, or profile URL; for posts, a shortcode or /post/ URL. tiktok: @handle, profile URL, or secUid; for posts, a video id or TikTok URL (short links included). x: screen name or profile URL; for posts, a tweet id or status URL. youtube: channel id (UC…), @handle, or channel URL; for posts, a video id or any YouTube URL.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| id | string | yes | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
get_post Get a post ~207
One post with its stats and author. Accepts a post id or any public URL. instagram: username or profile URL; for posts, a shortcode or /p/ or /reel/ URL. linkedin: profile slug or /in/ URL; for posts, an activity id or /posts/ URL. reddit: username, u/name, or profile URL; for posts, a t3_ id, bare id, or comments URL. threads: username, numeric user id, or profile URL; for posts, a shortcode or /post/ URL. tiktok: @handle, profile URL, or secUid; for posts, a video id or TikTok URL (short links included). x: screen name or profile URL; for posts, a tweet id or status URL. youtube: channel id (UC…), @handle, or channel URL; for posts, a video id or any YouTube URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
get_usage Check credit balance ~25
The calling key's credit balance and this month's usage by endpoint. Free to call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_user Get a profile ~221
A user's profile on any platform: follower counts, bio, verification, and platform extras under `extra`. Accepts a handle, id, or public URL. instagram: username or profile URL; for posts, a shortcode or /p/ or /reel/ URL. linkedin: profile slug or /in/ URL; for posts, an activity id or /posts/ URL. reddit: username, u/name, or profile URL; for posts, a t3_ id, bare id, or comments URL. threads: username, numeric user id, or profile URL; for posts, a shortcode or /post/ URL. tiktok: @handle, profile URL, or secUid; for posts, a video id or TikTok URL (short links included). x: screen name or profile URL; for posts, a tweet id or status URL. youtube: channel id (UC…), @handle, or channel URL; for posts, a video id or any YouTube URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
get_user_posts Get a user's posts ~230
A user's posts, newest first, with view, like, and comment counts. Pass the `next_cursor` from a previous response as `cursor` for the next page. instagram: username or profile URL; for posts, a shortcode or /p/ or /reel/ URL. linkedin: profile slug or /in/ URL; for posts, an activity id or /posts/ URL. reddit: username, u/name, or profile URL; for posts, a t3_ id, bare id, or comments URL. threads: username, numeric user id, or profile URL; for posts, a shortcode or /post/ URL. tiktok: @handle, profile URL, or secUid; for posts, a video id or TikTok URL (short links included). x: screen name or profile URL; for posts, a tweet id or status URL. youtube: channel id (UC…), @handle, or channel URL; for posts, a video id or any YouTube URL.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| id | string | yes | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
list_platforms List platforms ~24
The platforms Fetchwire serves and which of the six operations each one supports.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_routes List available routes ~107
Every route Fetchwire serves, with what each costs in credits. Free to call. Use it to find the routes the operation tools do not cover — TikTok's shop, live, and trending data, Reddit's subreddits and feeds, LinkedIn's jobs, Instagram's hashtags and places, X's communities and lists — then fetch one with call_route. Filter by `platform`, or by `contains` to match on the path.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | – | – | – |
| platform | – | – | – |
No output schema declared.
No examples provided.
search Search posts ~82
Search posts or videos by keyword on youtube, tiktok, instagram, x, or reddit. `sort` varies by platform — omit it for the default. LinkedIn and Threads have no keyword search; use list_routes to see what they do offer.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| platform | string | yes | – |
| q | string | yes | – |
| sort | – | – | – |
No output schema declared.
No examples provided.
search_users Search for accounts ~71
Find accounts by name or keyword on youtube, tiktok, instagram, x, reddit, or threads. Useful for turning a person or brand name into the handle the other tools take. LinkedIn has no profile search.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| platform | string | yes | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
What is the Fetchwire - Social Data MCP server?
Fetchwire - Social Data is an MCP server listed in the public MCP registry as dev.fetchwire/social-data. YouTube, TikTok, Instagram, X, Reddit, LinkedIn and Threads: public data in one schema. This page covers its hosted endpoint (https://mcp.fetchwire.dev/mcp).
Is the Fetchwire - Social Data MCP server safe to use?
Fetchwire - Social Data scores 63 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 Fetchwire - Social Data MCP server expose?
Fetchwire - Social Data exposes 10 tools: get_user, get_user_posts, get_post, get_comments, search, and 5 more. Their descriptions and schemas cost roughly 1,286 tokens of context every time the server is loaded.
Does the Fetchwire - Social Data MCP server require authentication?
No. We connected to Fetchwire - Social Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fetchwire - Social Data MCP server still maintained?
Fetchwire - Social Data is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.