Fetchwire - Social Data
REMOTE · MCP.FETCHWIRE.DEV · SCANNED OCT 7
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 2 Oct 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 22 to 25.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 2.
- 21 Sept 26 +9
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “search” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_comments” rewrote its description, which is the text the model reads security
- Tool “get_user_posts” rewrote its description, which is the text the model reads security
- Schema quality: 151 → 180 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Tool “get_comments” now declares an output schema ▲ functional
- Tool “get_post” now declares an output schema ▲ functional
- Tool “get_usage” now declares an output schema ▲ functional
- Tool “get_user” now declares an output schema ▲ functional
- Tool “get_user_posts” now declares an output schema ▲ functional
- Tool “list_platforms” now declares an output schema ▲ functional
- Tool “list_routes” now declares an output schema ▲ functional
- Tool “search_users” now declares an output schema ▲ functional
- First check of Tool coverage: 90 functional
- Schema quality: good → excellent functional
- New tool “search_posts” functional
- “call_route” reworded the description of “params” cosmetic
- “call_route” reworded the description of “path” cosmetic
- “get_comments” reworded the description of “cursor” cosmetic
- “get_comments” reworded the description of “id” cosmetic
- “get_comments” reworded the description of “platform” cosmetic
- “get_post” reworded the description of “id” cosmetic
- “get_post” reworded the description of “platform” cosmetic
- “get_user” reworded the description of “id” cosmetic
- “get_user” reworded the description of “platform” cosmetic
- “get_user_posts” reworded the description of “cursor” cosmetic
- “get_user_posts” reworded the description of “id” cosmetic
- “get_user_posts” reworded the description of “platform” cosmetic
- “list_routes” reworded the description of “contains” cosmetic
- “list_routes” reworded the description of “platform” cosmetic
- “search_users” reworded the description of “cursor” cosmetic
- “search_users” reworded the description of “platform” cosmetic
- “search_users” reworded the description of “q” cosmetic
- 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 7 Oct 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 | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 7ae4ccc7bfe669910a6ea12e9916b90c |
| SANs: fetchwire.dev, api.fetchwire.dev, mcp.fetchwire.dev, www.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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
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 | HTTP error | 404 | |
| 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 ~110
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 | – | – | Query parameters for that route, e.g. {'id': 'space'}. |
| path | string | yes | A path from list_routes, starting with /v1/. |
No output schema declared.
No examples provided.
get_comments Get comments on a post ~266
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. 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 | – | – | The `next_cursor` from a previous response. Omit for the first page. |
| id | string | yes | A handle, a platform id, or any public URL to the account or post. Parsed for you. |
| platform | string | yes | One of: youtube, tiktok, instagram, x, reddit, linkedin, threads. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| next_cursor | – | – | Opaque. Pass back as `cursor` to get the next page. Null when exhausted. |
| total | – | – | Total count when the platform reports one |
No examples provided.
get_post Get a post ~244
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 | A handle, a platform id, or any public URL to the account or post. Parsed for you. |
| platform | string | yes | One of: youtube, tiktok, instagram, x, reddit, linkedin, threads. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | – | – | – |
| category | – | – | – |
| created_at | – | – | Exact publish time when the platform exposes it |
| created_at_text | – | – | Platform's relative text such as '7 days ago' |
| duration_seconds | – | – | – |
| extra | object | – | – |
| id | string | yes | – |
| is_live | boolean | – | – |
| language | – | – | – |
| platform | string | yes | – |
| stats | – | – | – |
| tags | array | – | – |
| text | – | – | Description or body text |
| thumbnails | array | – | – |
| title | – | – | – |
| type | string | – | – |
| url | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| balance | integer | yes | Prepaid credits left on the account. Credits never expire. |
| by_endpoint | array | yes | – |
| credits_remaining | integer | yes | Same as balance, kept for older clients |
| credits_used | integer | yes | This month, across all keys of the same account |
| key_name | string | yes | – |
| period | string | yes | – |
No examples provided.
get_user Get a profile ~258
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 | A handle, a platform id, or any public URL to the account or post. Parsed for you. |
| platform | string | yes | One of: youtube, tiktok, instagram, x, reddit, linkedin, threads. |
| Name | Type | Req | Description |
|---|---|---|---|
| avatar_url | – | – | – |
| country | – | – | – |
| description | – | – | – |
| extra | object | – | – |
| followers | – | – | Subscribers on YouTube. Approximate unless exact is available. |
| handle | – | – | – |
| id | string | yes | – |
| joined_at_text | – | – | – |
| name | – | – | – |
| platform | string | yes | – |
| posts_count | – | – | – |
| url | – | – | – |
| verified | – | – | – |
| views | – | – | – |
No examples provided.
get_user_posts Get a user's posts ~261
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. 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 | – | – | The `next_cursor` from a previous response. Omit for the first page. |
| id | string | yes | A handle, a platform id, or any public URL to the account or post. Parsed for you. |
| platform | string | yes | One of: youtube, tiktok, instagram, x, reddit, linkedin, threads. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| next_cursor | – | – | Opaque. Pass back as `cursor` to get the next page. Null when exhausted. |
| total | – | – | Total count when the platform reports one |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| platforms | array | yes | – |
No examples provided.
list_routes List available routes ~141
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 | – | – | Match on the path, e.g. 'shop' or 'transcript'. |
| platform | – | – | Narrow to one of: youtube, tiktok, instagram, x, reddit, linkedin, threads. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| note | string | yes | – |
| routes | array | yes | – |
No examples provided.
search_posts Search posts ~137
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 | – | – | The `next_cursor` from a previous response. Omit for the first page. |
| platform | string | yes | One of: youtube, tiktok, instagram, x, reddit, linkedin, threads. |
| q | string | yes | The search text, as a person would type it. |
| sort | – | – | Platform-specific ordering. Omit for the platform's default. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| next_cursor | – | – | Opaque. Pass back as `cursor` to get the next page. Null when exhausted. |
| total | – | – | Total count when the platform reports one |
No examples provided.
search_users Search for accounts ~114
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 | – | – | The `next_cursor` from a previous response. Omit for the first page. |
| platform | string | yes | One of: youtube, tiktok, instagram, x, reddit, linkedin, threads. |
| q | string | yes | The search text, as a person would type it. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| next_cursor | – | – | Opaque. Pass back as `cursor` to get the next page. Null when exhausted. |
| total | – | – | Total count when the platform reports one |
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 23 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_posts, and 5 more. Their descriptions and schemas cost roughly 1,580 tokens of context every time the server is loaded.
Does the Fetchwire - Social Data MCP server require authentication?
Its publisher declares that Fetchwire - Social Data requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
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 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.