MIT
SocialCrawl
Officialby socialcrawl
Summary: This MCP server connects an AI agent to the SocialCrawl API so it can discover and pull live data from dozens of social, commerce, finance, jobs, travel and web platforms, with credit costs quoted before every call.
List platforms —
socialcrawl_list_platformsreturns all available platform names, endpoint counts and descriptions (no key needed).List endpoints —
socialcrawl_list_endpointsshows a platform's endpoints with required params, credit costs and response types.Fetch live data —
socialcrawl_requestcalls any endpoint to get profiles, posts, comments, search results, trending content, analytics, reviews, products/prices, app-store data, jobs/salaries, market data, congress trades and more.Retry safely — pass an
idempotencyKeytosocialcrawl_request; replays within 24h return the original response at 0 credits.Validate before spending — platform, resource and params are checked locally so bad calls fail free instead of burning credits.
Check credits —
socialcrawl_check_balanceshows remaining balance and recent deductions (0 credits).Read docs —
socialcrawl_get_docsreturns overview, full reference, authentication, credits, errors, idempotency, or per-platform docs.Cross-platform research — the agent can chain calls (e.g. compare follower counts across TikTok/Instagram/YouTube/X, or price-shop across Amazon, Walmart, Target and eBay).
Note: the supplied schema is the 1.x tool set (5 tools) covering 21 platforms; the README describes v2.0.0, which consolidates these into 7 tools (socialcrawl_find, socialcrawl_endpoint, socialcrawl_estimate, socialcrawl_request, socialcrawl_collect, socialcrawl_account, socialcrawl_manage) across a much larger platform catalogue.
Provides access to Amazon Shop pages data through the SocialCrawl API, allowing retrieval of product and store information from the Amazon platform.
Enables retrieval of Facebook profiles, posts, reels, photos, groups, and Ad Library data through 12 endpoints, providing comprehensive social media data from the Facebook platform.
Provides access to Google Search and Ad Library data through 4 endpoints, enabling search functionality and advertising insights from the Google platform.
Allows retrieval of Instagram profiles, posts, reels, comments, highlights, and search results through 12 endpoints, providing comprehensive Instagram social media data.
Provides access to Kick clips data through a single endpoint, enabling retrieval of video content from the Kick streaming platform.
Enables retrieval of Linktree link pages data through a single endpoint, providing access to link aggregation profiles from the Linktree platform.
Provides access to Pinterest search, pins, and boards data through 4 endpoints, enabling retrieval of visual content and collections from the Pinterest platform.
Allows retrieval of Reddit subreddits, posts, comments, search results, and ads through 7 endpoints, providing comprehensive forum and community data from Reddit.
Provides access to Snapchat profiles data through a single endpoint, enabling retrieval of user profile information from the Snapchat platform.
Enables retrieval of Threads profiles, posts, and search results through 5 endpoints, providing access to Meta's Threads social media platform data.
Provides comprehensive access to TikTok data through 26 endpoints including profiles, videos, comments, followers, search, trending content, live streams, Shop, and showcase data.
Allows retrieval of Twitch profiles and clips data through 2 endpoints, providing access to streaming platform data from Twitch.
Enables retrieval of YouTube channels, videos, shorts, playlists, comments, trending content, and comment replies through 12 endpoints, providing comprehensive YouTube platform data.
socialcrawl-mcp
Give your AI agent access to every SocialCrawl platform and endpoint — social media, commerce, marketplaces & product reviews, retail, app stores, places, travel & local, business & software reputation, jobs & salaries, markets & finance, congressional trading disclosures, news, web research, full web scraping & browser automation, on-page SEO, prediction markets, search trends, cross-platform Prism composites, and a universal meta-search — through a single API, with exact credit pricing for every endpoint
Installation | Overview | Setup | Usage | Tools | Platforms
Installation
Remote server (hosted — no install)
Connect straight to the hosted Streamable HTTP endpoint — nothing to install or run:
Claude Code (works in the CLI and Claude Code on the web / cloud sandboxes)
claude mcp add --scope user --transport http socialcrawl https://mcp.socialcrawl.dev/mcp \
--header "Authorization: Bearer sc_your_key_here"Any client that reads .mcp.json
{
"mcpServers": {
"socialcrawl": {
"type": "http",
"url": "https://mcp.socialcrawl.dev/mcp",
"headers": { "Authorization": "Bearer ${SOCIALCRAWL_API_KEY}" }
}
}
}Cursor / Windsurf / VS Code — choose the HTTP ("streamable-http") server type with the same URL and header. x-api-key: sc_your_key_here works as an alternative header.
The discovery tools (socialcrawl_find, socialcrawl_endpoint, socialcrawl_estimate) work without a key, so you can explore before signing up. claude.ai custom connectors (Settings → Connectors) require OAuth. An OAuth 2.1 resource-server mode is in preview and off by default (SOCIALCRAWL_OAUTH=1; see docs/REMOTE-STREAMABLE-HTTP.md); until it is enabled on the hosted server, use the header-based setup above.
Prefer running it locally? Every stdio option below works exactly as before.
npm
npm install -g socialcrawl-mcpAvailable on npm. Most users don't need this — the MCP client configs below use npx and auto-install on first run.
Claude Code (quickest)
claude mcp add --scope user socialcrawl -e SOCIALCRAWL_API_KEY=sc_your_key_here -- npx -y socialcrawl-mcpClaude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"socialcrawl": {
"command": "npx",
"args": ["-y", "socialcrawl-mcp"],
"env": {
"SOCIALCRAWL_API_KEY": "sc_your_key_here"
}
}
}
}Cursor
Add to .cursor/mcp.json in your project root or ~/.cursor/mcp.json globally:
{
"mcpServers": {
"socialcrawl": {
"command": "npx",
"args": ["-y", "socialcrawl-mcp"],
"env": {
"SOCIALCRAWL_API_KEY": "sc_your_key_here"
}
}
}
}VS Code (Claude Code)
Add to .vscode/mcp.json in your project or your user settings:
{
"servers": {
"socialcrawl": {
"type": "stdio",
"command": "npx",
"args": ["-y", "socialcrawl-mcp"],
"env": {
"SOCIALCRAWL_API_KEY": "sc_your_key_here"
}
}
}
}Windsurf
Add to your Windsurf MCP configuration:
{
"mcpServers": {
"socialcrawl": {
"command": "npx",
"args": ["-y", "socialcrawl-mcp"],
"env": {
"SOCIALCRAWL_API_KEY": "sc_your_key_here"
}
}
}
}Other MCP-compatible clients
Any MCP client that supports stdio transport can use this server. The general pattern is:
Command:
npxArgs:
["-y", "socialcrawl-mcp"]Environment:
SOCIALCRAWL_API_KEYset to your API key
Restart your AI client after saving the configuration.
Related MCP server: BulkPublish
Overview
socialcrawl-mcp is an MCP (Model Context Protocol) server that connects AI agents to the SocialCrawl API — a unified data API over social, commerce, jobs, finance, research and web data. socialcrawl_find with no task lists every platform; socialcrawl_account view freshness shows the live counts.
Retrieve profiles, posts, comments, search results, trending content, and analytics from TikTok, Instagram, YouTube, Twitter/X, LinkedIn, Reddit, Threads, Douyin, Xiaohongshu, Telegram, Quora, Bluesky, Apple Music, GitHub, Hacker News, Product Hunt, Polymarket, and many more platforms. Pull products, offers, price history, reviews, and sellers from Amazon, Walmart, Target, Home Depot, eBay, Klarna, AliExpress, Etsy, Sephora, H&M, Kohl's, Wayfair, Gumtree, and Google Shopping; apps, charts, and reviews from Google Play and the Apple App Store; hotels, restaurants, attractions, cruises, and traveler reviews from Tripadvisor, plus local business data from Yelp and Google Business; brand reputation from Trustpilot and software reviews from G2; job listings and salary bands from LinkedIn, Indeed, Bing, and Xing; market quotes, price history, financial statements, and options chains; US congressional trading disclosures; Korean search and Data Lab trend series from Naver; cross-web brand mentions with sentiment via Content Analysis; Google News headlines and Google Trends interest curves — plus web research via Tavily and Perplexity, AI-powered X search via Grok, on-page SEO audits, and a single /search/everywhere endpoint that fans out across 14 sources in one call.
New in v2.0.0: seven tools instead of eleven (socialcrawl_find, socialcrawl_endpoint, socialcrawl_estimate, socialcrawl_request, socialcrawl_collect, socialcrawl_account, socialcrawl_manage). See Available Tools for the 1.x → 2.0 mapping and CHANGELOG.md for every release.
What the MCP server does:
Finds the right endpoint for a task in plain words (ranked search across every endpoint, with URLs and handles resolved), and tells the agent what data each one returns
Fetches live data on your behalf across every platform, method, and composite
Prices every call up front — ladder, flat, or metered band — so an agent can budget before it spends
Validates requests locally before calling the API: required params,
oneOfgroups, enum values, integer ranges, parameter couplings, and CSV limits. A bad call fails free instead of burning creditsProvides built-in API documentation the agent can query on demand, paged rather than truncated
Setup
1. Get your API key
Sign up at socialcrawl.dev and grab your API key from the dashboard. Every account starts with 100 free credits — no credit card required.
2. Add the key to your config
Replace sc_your_key_here in the installation config above with your actual API key (starts with sc_).
TIP
You can also setSOCIALCRAWL_API_KEY as a system environment variable instead of putting it in the MCP config. The discovery and documentation tools work even without a key — only actual API requests need one.
Usage
Ask your AI agent in natural language. The MCP server handles the rest.
Fetch a profile
Get the TikTok profile for @charlidamelioThe agent calls socialcrawl_request with platform: "tiktok", resource: "profile", params: { handle: "charlidamelio" } and returns structured profile data including followers, bio, verification status, and engagement metrics.
Search across platforms
Search YouTube for "machine learning tutorials"Get post comments
Get the comments on this Instagram post: https://instagram.com/p/CwA1234abcdCross-platform research
Compare the follower counts of @mkbhd on TikTok, Instagram, YouTube, and TwitterThe agent makes 4 sequential API calls — one per platform — and compiles the results into a comparison.
Shop across retailers
Find the cheapest 65-inch OLED TV across Amazon, Walmart, Target, and eBayExplore available endpoints
What social media platforms can you access?Show me all the TikTok endpointsWhich endpoints can give me video transcripts?Each is a socialcrawl_find call: the task in plain words, ranked across every endpoint, no platform needed.
Learn the API from the API
How do I get started with SocialCrawl?Show me exactly how to call the Prism comments endpointIs this MCP server's endpoint list up to date?These hit socialcrawl_endpoint and socialcrawl_account and cost nothing.
Check what something costs before running it
What would it cost to run a Prism brand-mentions report?Show me everything I can call for 1 creditWhy did that last call charge me 7 credits instead of 2?The first two hit socialcrawl_estimate; the third reads the credit ledger via socialcrawl_account with view: "transactions" and shows the deduction and refund rows for that request_id.
Access documentation
How does the SocialCrawl credit system work?How do I page through a list endpoint?Example response
Every response follows a unified envelope format:
{
"success": true,
"platform": "tiktok",
"endpoint": "/v1/tiktok/profile",
"data": {
"content": { "text": "...", "media_urls": ["..."] },
"author": { "username": "charlidamelio", "followers": 156000000 },
"engagement": { "likes": 5200, "engagement_rate": 0.045 },
"metadata": { "language": "en", "content_category": "entertainment" }
},
"credits_used": 1,
"credits_remaining": 99
}NOTE
The same response structure is returned for every platform — no per-platform parsing logic needed.
Available Tools
Version 2.0.0 exposes 7 tools (about 4.7k tokens of tools/list, down from about 12.8k for the 11 tools of 1.x):
Tool | What it does | Needs API key? |
| Start here. A task in plain words becomes the best endpoints (3 by default), each with the params the task already supplies (URLs and | No |
| The contract for one endpoint ( | No |
| Exact cost before you spend: one call ( | No |
| Call one endpoint: | Yes |
| Walk a paged endpoint until | Yes |
| Free checks: | Yes (except |
| Stateful work by | Yes |
Upgrading from 1.x. Set SOCIALCRAWL_LEGACY_TOOLS=1 to also register the nine retired 1.x names as thin wrappers for this major version. The mapping:
1.x tool | 2.0 tool |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| unchanged ( |
Discovery, live and bundled
socialcrawl_find, socialcrawl_endpoint and socialcrawl_estimate answer from data bundled with the server (generated from the backend registry, dump schema v4) and need no key. With a key they first ask the API's free /v1/utility/* routes (find, resolve, endpoint, estimate), which answer from the live registry, and fall back to the bundled answer when a route is not deployed. Every one of these is 0 credits.
Why freshness matters. This server ships a catalogue generated when it was built; the API keeps moving. Data calls always hit the live API and keep working, but discovery, pricing and local validation answer from that snapshot. The server checks this itself once per process and, when it is behind, adds one line to the next tool result. One free call tells you which situation you are in:
socialcrawl_account view: "freshness"These same endpoints are plain HTTP, so a third-party integration or a non-MCP agent framework gets the identical information with a curl.
Pricing — know the cost before you spend
socialcrawl_estimate exists because a single number is a lie for most of the surface. SocialCrawl bills three ways:
Ladder — the tier rate per request: standard 1cr, advanced 5cr, premium 10cr.
Flat (some of them free) — a per-endpoint override, e.g.
/v1/search/everywhereat 20cr flat.Metered — the charge depends on the request. An upfront ceiling is deducted and refunded down to the work actually done.
Quoting a metered endpoint's base cost understates every call: /v1/search/news has a 1cr base but really charges 2–62cr — one credit per Google country leg that returns articles, plus per-article billing when the bing engine is added. The tool returns the real band, the registry's own charging rule, the parameters that move the bill, and the worst case to budget for:
action: "overview" → ladder, every free endpoint, every flat override, every metered band + rule, cache TTLs, full refund matrix
action: "endpoint" → one endpoint's price, rule, price-driving params, paging cost, worst case
action: "platform" → a whole platform's cost table
action: "list" → rank/filter by cost — "everything I can call for 1 credit", "the 10 most expensive endpoints"
action: "hydration" → every include= row join: what it fills, per-row rate, row cap, fully-joined ceiling
action: "judgments" → every judged list: free default labels/relevance, metered presets, the hold per opt-inPass the include you intend to send to action: "endpoint" and the band becomes arithmetic — the exact hold, itemised per join, using the same formula the backend's pricer runs:
action: "endpoint", platform: "linkedin", resource: "search/people", include: "profile", rows: 3
→ holds 22 credits (10cr page + 12cr for 3 rows of `profile`), settling anywhere down to 10Or pass the exact params you will send (and calls, for a whole job). Joins, metered judgments and max_pages are all itemised, and max_pages multiplies the page, because each page walked is billed as one call:
action: "endpoint", platform: "youtube", resource: "search", calls: 10,
params: { query: "espresso", include: "engagement,channel", label: "mention", brand: "Acme", max_pages: "3" }
→ 1cr page + 5cr engagement + 5cr channel + 4cr label=mention = up to 15cr per page
× 3 pages = up to 45cr per call; 10 calls = up to 450 credits held, settling to what was filled and judgedIt also states the rules that make the real charge differ from the sticker price. Cache hits, idempotent replays, empty results, upstream failures and dry_run=1 previews are all 0 credits; seen=<id> discounts each page by its share of rows you already received; since / stop_at_id end a walk at rows you already hold.
Judgments — labels and relevance, free by default
About 50 list endpoints judge their rows for you at no extra credit. Posts carry sponsored, intent and niche; comments carry sentiment, question, purchase_intent and complaint; reviews carry sentiment and issue. All of these land under computed.labels, and the judged searches score each row's relevance to your query under computed.relevance. Only these add credits:
a metered preset:
mention(withbrand=),quality,injectionon posts;spam,toxic,low_qualityon comments;reports,incentivizedon reviews,label=intentwithoffer=(what you sell),relevance=score|filterwith your own topic inrelevant_to=.
Each holds 1 credit per started 25 rows of the page (4cr on a 100-row page) and settles to the rows judged fresh. Already-judged rows and cached pages are free. judgments=off turns the defaults off, and dry_run=1 previews the cost for 0 credits. socialcrawl_endpoint with id: "judgments" is the full contract.
Row hydration — one call instead of a page plus a lookup per row
Some lists are thin because the upstream publishes nothing else on them: a Pinterest search result has no save count, a LinkedIn reactor row no follower count, a YouTube playlist no view counts or durations. Another SocialCrawl endpoint answers each of those for one row — so those endpoints accept an include= token that joins every row to that sibling in the same call.
GET /v1/pinterest/search?query=kitchen&include=engagement → saves, likes, comments, shares on every row
GET /v1/youtube/playlist?playlistId=PL...&include=engagement,channel
GET /v1/linkedin/search/people?keywords=cto&include=profile&limit=3Opt-in. No token, no join, no extra credit, no extra latency — a caller who never asks pays exactly what they always paid.
Billed per row actually filled. The ceiling is held up front; a credit is kept only for a row a fresh sibling lookup filled. Rows served from the sibling's cache are free, unfillable rows are refunded, and a page that joined in full is cached whole, so an immediate repeat is 0 credits.
A row cap caps the bill.
limit=3&include=profileon LinkedIn holds 22 credits, not 50.It tells you what it did.
data.hydrationreports rows, lookups, cache hits, credits held vs kept, and milliseconds;_warningscarries<token>_partialwhen only some rows filled.
socialcrawl_endpoint with id: "hydration" lists every join, its price and the full contract; socialcrawl_estimate quotes one call with its include.
Monitors — schedule any recipe
socialcrawl_manage with area: "monitors" wraps any registry endpoint or Prism composite in a scheduled, stateful monitor (/v1/monitors/*). It re-runs the recipe hourly/daily/weekly (or on a cron), delivers each result to an HMAC-signed webhook, raises alerts on metric thresholds or changes, and keeps a per-run time-series you can read back. "Prism answers once; monitors watch it for you." Managing monitors costs 0 credits; each scheduled run bills the recipe's normal cost plus a 1-credit scheduling premium. See socialcrawl_endpoint with id: "monitors" for the full contract.
Web — scrape, crawl, browse
socialcrawl_manage with area: "web" drives the full web-scraping and browser-automation surface (the web platform, /v1/web/*) through a single action parameter:
Sync reads —
scrape(URL → markdown/HTML/screenshot/links),search(web search with page content),map(discover a site's URLs),extract(LLM structured data from a page).Async jobs —
crawla whole site,batch_scrapemany URLs, oragent(autonomous multi-step web task); each returns a job you poll withjob_get/job_list, inspect withjob_errors(per-page failures), and stop withjob_cancel.crawl_previewdry-runs a crawl's parameters for free before you pay for it.Monitors —
monitor_create/list/get/update/delete/checksre-check a URL on a cadence and deliver changes to a webhook.Sessions —
session_create/get/list,session_execute(run code in the live page),session_close.
Most of the paid web surface is metered rather than flat: a crawl holds limit credits and refunds every page it did not crawl; a session holds against ttl_seconds and settles on close. Job, monitor, and session management is 0 credits. See socialcrawl_endpoint with id: "web", or socialcrawl_estimate with id: "web".
Smart validation
Before making any API call, socialcrawl_request mirrors the backend's own pre-billing validator against the bundled registry data: the platform and resource exist, required parameters and oneOf groups are satisfied, enum values are legal, integers sit inside their declared range, parameter couplings hold (order needs sort; Reddit's timeframe needs sort=top), and CSV lists are within their entry limits. A malformed call fails instantly and for free instead of costing a round trip — and an agent gets told exactly what to fix rather than looping on a call that can never succeed.
Retry-safe requests
Pass an idempotencyKey to socialcrawl_request (UUIDv4 recommended) to make the call retry-safe. If the request is replayed within 24h, the server returns the original response and deducts 0 credits (X-Idempotent-Replay: true).
Supported Platforms
Platform | Data Available |
Profiles (single sub-resources or one-call bundles: all, complete, with-posts) & company pages (incl. lookup by domain, also-viewed, employee counts), posts & post-with-comments, reposts, reactions, comments & replies, Pulse articles with comments and reactions, people search (keyword or search-URL), company & hashtag search, similar members, profile sub-resources (experience, education, skills, position skills, certifications, followed schools/newsletters/Top Voices, last activity…), jobs (search, company jobs, jobs a member posted, hiring team, details), company insights, groups, the complete post-history archive (metered per post), transcripts, Ad Library, profile-360 | |
Prism | Cross-platform composites — URL lookup, comment harvesting, batch post-stats/profile/comment lookup, async background jobs of up to 5,000 items, handle-audit, name→accounts resolution (find-accounts), handle/link mentions, adverse-post screening, campaign-brief checks, hook/format lift, term earliness, a no-keyword country trend board, commenter language mix, comment-sourced buyer leads, brand mentions, demand signals, AI visibility, crisis radar/post-mortem, reputation, share-of-voice, creator vetting & creator cards, org radar, Korea gap, AI consensus answers, video/app/product intelligence |
Profiles, account transparency (profile/about), posts, reels, comments & comment replies, highlights, stories, tagged & location feeds, followers/following, similar accounts, post likers, reshare stats, one-call reels/posts feeds with share counts, engagement analytics, universal + popular-post search, reels/hashtag/profile/location/music search (reel search with creator cards via | |
TikTok | Profiles, videos, comments & replies, on-screen text extraction, keyword/hashtag/user/music search + suggestions, hashtag details, trending (global or in-country For You), TikTok's own popular-hashtag and Top Videos boards, audience, similar accounts, followers, liked videos, playlists & collections, place feeds, effects, live, songs, transcripts, Ad Library, profile-360 |
Pages, groups & group posts, posts, comments & replies, photos, reels (incl. full reels feed with view counts), events & event search, Marketplace, keyword search over posts/pages/people/videos/groups, transcripts, full Ad Library | |
YouTube | Channels, videos, shorts, comments & replies, sponsors, playlists & items, community posts, search (advanced + autocomplete), trending, live streams, channel contact email lookup, media files (audio/video/subtitles/thumbnails), transcripts, batch videos/channels/transcripts, profile-360 |
Web Scraping | Scrape, web search, site map, LLM extract, async crawl/batch-scrape/agent jobs with per-page error feeds, change monitors, interactive browser sessions, document parse — driven by |
US Congress Trades | US Congress STOCK Act disclosures — trade feeds (all/48h/7d), members, per-politician and per-ticker stats and trades, state delegations, and the full statistics suite (party, sectors, issuers, volume, unusual activity, buy/sell ratio, late filings) |
Klarna | Product details and every merchant offer, keyword search + suggestions, user and professional reviews with score overviews, price history, product comparison, category browsing with filters/keywords/buying guides, store listings |
Tripadvisor | Hotels, restaurants, attractions and cruise ships — search and full detail for each, traveler reviews with owner replies, place lookup by URL, destination autocomplete, experience types |
Twitter/X | Profiles, tweets and replies, tweet & user search, user media, followers, following, retweeters, communities, video transcripts, AI search via Grok, profile-360 |
Naver | Korea's #1 portal — blog, news, encyclopedia, cafe, KiN, local, image, web search, errata & adult classifiers, Data Lab search-trend & shopping-insight series, brief |
Subreddits, post detail, comments, user profiles with post and comment history, keyword/comment/media search, subreddit discovery, transcripts, omni-search VoC sweep | |
GitHub | Users, repos, issues, PRs, READMEs, releases, search, repo dossier, user profile-velocity |
Gumtree | UK classifieds — listing search and details, similar listings, seller profiles and their ads, search suggestions, trending searches, category tree with filters, location lookup |
Jobs | Job search and listing detail across LinkedIn, Indeed, Bing and Xing, LinkedIn organization-id resolution, and salary ranges by title and country |
Sephora | Product details, reviews, keyword search + suggestions, category tree browsing, brand listings and per-brand products, store lookup, per-SKU in-store availability |
Content Analysis | Cross-web brand mentions, sentiment, rating distributions, phrase/category trends |
Web search, Ads Transparency, Business Profile (info, reviews, updates, Q&A), Travel hotels | |
AliExpress | Product details, keyword search, similar products, reviews, per-SKU shipping, hot products, featured promotions, category tree |
Apple App Store | App search, search suggestions, app details, reviews, charts, listings database, reference data |
Google Play | App search, search suggestions, app details, reviews, charts, listings database, reference data |
Amazon | Product search, ASIN details, reviews, sellers, shop pages, Best Sellers charts, current deals, seller profiles — ~13 marketplaces |
Douyin | China's TikTok — video search, creator profiles and feeds, video detail, comments and comment replies, creator search, hot-search board (mostly metered per row) |
Finance | Instrument quotes, ticker search, markets overview, instrument news, daily price history, company financial statements, options chains |
G2 | Software marketplace — product pages, reviews, category listings and the category index, vendor profiles and their catalogue, product URL index |
Quora | Question search and detail, answer search, Space post search, profile search, Space/topic search |
H&M | Keyword search + suggestions, store listings by country, countries/languages, category tree, per-product supplier and factory disclosure |
Pins, boards, user boards, search, Pinterest Trends by country, URL save-counts | |
Spotify | Artists, tracks, albums, podcasts, episodes, search |
Threads | Profiles, posts, post comments, keyword search, user search |
Utility | Free API self-discovery — quickstart, endpoint catalogue, per-endpoint usage guide, cross-cutting capabilities index, plain-words call planner, LLM context payload. 0 credits, served from the live registry. Behind |
Xiaohongshu | RED / Little Red Book — note search, hot-search board, creator profiles and their notes, note detail, top-level comments (5cr per returned row) |
Apple Music | Catalog search, artist, album, track, per-country charts (songs, albums, music videos, playlists) |
Google Shopping | Product search, product details, price history, cross-retailer reviews, per-seller offers |
Kohl's | Keyword search, reviews, product questions and answers, store lookup, category tree |
Rumble | Search, channel videos, video details, comments, transcripts |
Target | Product details by TCIN, reviews, category browsing, full taxonomy, store lookup |
TikTok Shop | Products, reviews, listings, search, creator showcases |
Universal Search | One query fanned out across many platforms (20cr flat); |
Walmart | Product details, reviews, keyword search, category browsing, seller offers |
Yelp | Business profiles by encid, business reviews, business search (compact and full-card), search suggestions |
Bluesky | Profiles, user posts, post details, keyword post search |
Etsy | Listings by id or URL, a shop's catalogue, similar listings, search suggestions |
Hacker News | Story search, story, comment tree, profile |
Home Depot | Keyword search, product details by item id or URL (store/zip-aware pricing), reviews, store lookup by ZIP |
Tavily | Web search (with LLM answer), URL extraction, sitemap, full crawl |
Twitch | Profiles, clips, videos, schedules |
Google Trends | Interest-over-time (explore), rising/breakout related queries, and Trending Now by location |
Kwai | Profiles, posts |
Telegram | Public channel profiles, channel post feeds, single post lookup |
Truth Social | Profiles, posts |
Wayfair | Product search, product details by SKU, reviews |
eBay | Listing search incl. sold/completed with realised prices, listing details |
Snapchat | Profiles, Spotlight comments |
Trustpilot | Business search, company reviews |
Google News | Real-time Google News SERP search |
Kick | Clips |
Komi | Link pages |
LinkBio | Link pages |
LinkMe | Link pages |
Linktree | Link pages |
On-Page | Single-URL on-page SEO audit — the technical, content and meta checks in one call |
Perplexity | Sonar web research with cited sources |
Pillar | Link pages |
Polymarket | Prediction-market research — multi-query fan-out + ranking |
Product Hunt | Current Product Hunt launches (~50 per page), optionally by topic |
socialcrawl_find with no task lists every platform with its live endpoint count.
Error Handling
The MCP server handles errors gracefully and gives the agent actionable guidance. Every API error passes the server's own error.message through, followed by reason: … when the API names one and request_id: req-… on its own line (read from the body, or the X-Request-Id header when the body is not JSON). Quote the request_id when you report a problem: it is how a call is found in the logs and the credit ledger.
Error | What the agent sees |
Missing API key | Prompts to set |
Invalid API key | Asks to check the key configuration |
Insufficient credits | Shows balance and links to billing page |
Bad platform/resource | Suggests using discovery tools to find the right endpoint |
Missing parameters | Lists exactly what's missing with examples — caught locally, before billing |
Invalid parameter value | Names the illegal enum value, out-of-range integer, broken coupling, or over-long CSV — caught locally, before billing |
Resource not found (404) | The server's reason the item is missing (e.g. |
Idempotency-Key conflict (409) | Tells the agent the key was used by another account — generate a fresh one |
Idempotency-Key payload mismatch (422) | Tells the agent the same key was reused with different params |
Method not allowed (405) | Reports the wrong HTTP method for that route |
Payload too large (413) | Request body over the JSON size cap; rejected before parse |
Rate limited (429) | Over the 600 req/min per-key window — unbilled; back off and retry |
Concurrency limit (429) | Asks the caller to back off (50 concurrent/key max) |
Key budget exceeded (402) | This key's own spend cap is spent while the account still has credits — raise the cap, don't top up |
Upstream error (502) | The server's account of which platform failed, the refund, and when to retry |
Platform unavailable (503) | The server's cause (circuit breaker open or upstream throttling) and retry hint; credits refunded |
Links
Get Your API Key — 100 free credits, no credit card required
API Documentation — full endpoint reference, credits, and error codes
Available Tools
5 toolssocialcrawl_get_docsGet SocialCrawl DocumentationARead-onlyIdempotent
Retrieve SocialCrawl API documentation. Topics: 'overview' (compact intro), 'full' (comprehensive reference), 'authentication', 'credits', 'errors', or any platform slug (e.g., 'tiktok') for platform-specific docs. No API key required.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Documentation topic: 'overview', 'full', 'authentication', 'credits', 'errors', 'idempotency', or a platform slug (e.g., 'tiktok') | overview |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, non-destructive, idempotent, and closed-world behavior. The description adds valuable context beyond this by specifying that no API key is required, which is a useful operational detail not covered by annotations, though it does not mention rate limits or response formats.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized and front-loaded, starting with the core action ('Retrieve SocialCrawl API documentation') followed by specific details. Every sentence adds value, such as listing topics and noting the lack of API key requirement, with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (1 parameter, no output schema) and rich annotations, the description is mostly complete. It covers purpose, usage, and key behavioral aspects like no API key needed, but could slightly improve by hinting at the output format or linking to sibling tools for related actions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents the 'topic' parameter with its default and allowed values. The description adds minimal extra meaning by listing example topics like 'credits' and 'errors', but this largely overlaps with the schema's description, resulting in a baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'retrieve' and the resource 'SocialCrawl API documentation', specifying what the tool does. It distinguishes from siblings by focusing on documentation retrieval rather than balance checking, endpoint listing, platform listing, or API requests.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on when to use this tool by listing specific topics (e.g., 'overview', 'authentication', platform slugs) and noting 'No API key required'. However, it does not explicitly state when not to use it or name alternatives among siblings, such as using socialcrawl_list_endpoints for endpoint details instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
socialcrawl_list_endpointsList Endpoints for a PlatformARead-onlyIdempotent
List all available endpoints for a specific platform with required parameters, credit costs, and response types. No API key required.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| platform | Yes | Platform slug (e.g., 'tiktok', 'instagram', 'youtube') |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations, specifically the auth requirement ('No API key required') and the nature of the response (endpoint details, credit costs, response types). This helps the agent understand what to expect without duplication.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the core action ('List all available endpoints') and packs all key details efficiently. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, clear schema, annotations) and no output schema, the description adequately explains what the tool returns (endpoints with parameters, costs, response types). It is complete enough for an agent to use correctly without additional documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides full coverage for the single parameter 'platform' with a description and enum. The description adds no additional parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'List all available endpoints for a specific platform' with specific content details (required parameters, credit costs, response types). This distinguishes it from siblings like socialcrawl_list_platforms (lists platforms) and socialcrawl_request (makes requests).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context about when to use the tool: it is for discovering endpoints for a specific platform, and it notes that no API key is required. It does not explicitly compare to alternatives, but the sibling names and description make the intended use obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
socialcrawl_list_platformsList SocialCrawl PlatformsARead-onlyIdempotent
List all 21 social media platforms available through SocialCrawl. Returns platform names, endpoint counts, and descriptions. No API key required.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds value by specifying that no API key is required and detailing the return content (endpoint counts, descriptions), which is useful behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: three short sentences that front-load the main purpose and then provide key details (return fields, no API key). Every sentence adds value with no redundancy or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with no parameters, no output schema, and clear annotations, the description is complete. It states the exact number of platforms, what is returned, and that authentication is not required – all an agent needs to select and invoke this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the input schema is empty. The description does not need to explain parameters, and the baseline for zero-parameter tools is 4. The description adds no parameter semantics because there are none to describe.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the action (List), the resource (all 21 social media platforms), and the scope (available through SocialCrawl). It also specifies what is returned (names, endpoint counts, descriptions), clearly distinguishing it from sibling tools like `socialcrawl_list_endpoints` which list endpoints instead.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use this tool: when you need a list of the 21 SocialCrawl platforms. However, it does not explicitly mention alternatives or when not to use it, such as pointing to `socialcrawl_list_endpoints` for endpoints. The usage context is implied rather than explicitly guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
socialcrawl_requestMake a SocialCrawl API RequestARead-onlyIdempotent
Make an API request to any SocialCrawl endpoint. Fetches real-time social media data (profiles, posts, comments, search results, analytics) from 21 platforms. Requires a valid SOCIALCRAWL_API_KEY. Validates platform, resource, and parameters before making the call to avoid wasting credits. Pass an optional idempotencyKey to make the request retry-safe (replays return the original response and deduct 0 credits).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| platform | Yes | Platform slug (e.g., 'tiktok', 'instagram', 'youtube') | |
| resource | Yes | Resource path (e.g., 'profile', 'post/comments', 'search') | |
| params | No | Query parameters as key-value pairs (e.g., { handle: 'charlidamelio' }) | |
| idempotencyKey | No | Optional Idempotency-Key header. Lets you safely retry the same request — replays return the original response and deduct 0 credits (24h TTL). |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds valuable behavioral context beyond annotations: it explains the API key requirement (auth needs), mentions credit conservation ('avoid wasting credits'), and details idempotency behavior ('replays return the original response and deduct 0 credits'). While annotations cover readOnly, non-destructive, idempotent, and open-world hints, the description provides practical implementation details that enhance understanding.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is efficiently structured with three sentences that each serve distinct purposes: stating the core function, listing data types and requirements, and explaining validation and idempotency benefits. Every sentence adds value without redundancy, making it appropriately sized and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (4 parameters, open-world API) and rich annotations, the description provides good contextual coverage. It explains authentication, credit management, and idempotency - key aspects for API usage. The main gap is lack of output information (no output schema), but the description compensates reasonably well for a general-purpose API tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions 'validates platform, resource, and parameters' and explains the idempotencyKey benefit, but doesn't provide additional meaning for platform, resource, or params beyond what's in their schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verbs ('Make an API request', 'Fetches real-time social media data') and resources ('any SocialCrawl endpoint', '21 platforms', 'profiles, posts, comments, search results, analytics'). It distinguishes itself from siblings by being the primary request-making tool rather than checking balance, getting docs, or listing endpoints/platforms.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context about when to use this tool ('Make an API request to any SocialCrawl endpoint') and mentions prerequisites ('Requires a valid SOCIALCRAWL_API_KEY'). However, it doesn't explicitly state when to use alternatives like socialcrawl_list_endpoints for discovery or socialcrawl_check_balance for credit monitoring, leaving some guidance gaps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
v1.2.0- First observed
socialcrawl_check_balance - First observed
socialcrawl_get_docs - First observed
socialcrawl_list_endpoints - First observed
socialcrawl_list_platforms - First observed
socialcrawl_request
TDQS
A4.4/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: check_balance for account credits, get_docs for API documentation, list_endpoints for platform-specific endpoints, list_platforms for available platforms, and request for making API calls. An agent can easily differentiate them based on their unique functions.
Naming Consistency5/5
All tools follow a consistent snake_case pattern with a 'socialcrawl_' prefix and descriptive verb_noun combinations (e.g., check_balance, get_docs, list_endpoints). This uniformity makes the tool set predictable and easy to navigate.
Tool Count5/5
With 5 tools, this server is well-scoped for its purpose of interacting with the SocialCrawl API. It covers essential functions like checking credits, accessing documentation, listing platforms/endpoints, and making requests, without being overly sparse or bloated.
Completeness5/5
The tool set provides complete coverage for the SocialCrawl API domain: it includes meta operations (balance, docs, platforms/endpoints listing) and core functionality (making API requests). There are no obvious gaps, as agents can perform all necessary actions from exploration to data retrieval.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive
Related MCP Connectors
- OutstandOAuthso.outstand
Publish and schedule social media posts and read analytics across 12 networks through one API.
Instagram, TikTok, Threads, Bluesky and 8 more: one API, one key, one JSON shape
Unified social-media data across 10 networks: profiles, posts, search, comments, cross-search.
Social media data: 85 tools across 11 platforms (YouTube, TikTok, Instagram, X & more), one key.
Related MCP Servers
- AlicenseAqualityAmaintenanceThe best free social media publishing and scheduling API. Publish to 11 platforms from a single API call. Schedule posts, upload media, track analytics, and automate your social media workflow.512MIT
- AlicenseNot gradedqualityDmaintenanceReal-time X/Twitter social intelligence for AI agents and developers, powered by Grok's live search capabilities.21 npm3MIT
- AlicenseAqualityDmaintenanceProvides AI agents with unified access to 21 social media platforms and 105 endpoints for retrieving profiles, posts, comments, search results, trending content, and analytics without per-platform authentication.4895 npmMIT
socialcrawl_check_balanceCheck SocialCrawl Credit BalanceARead-onlyIdempotent
Check the remaining credit balance and recent deductions for the authenticated SocialCrawl account. Calls the meta endpoint GET /v1/credits/balance — costs 0 credits. Requires a valid SOCIALCRAWL_API_KEY.
No parameters
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds valuable context beyond this: it specifies the API endpoint called (GET /v1/credits/balance), notes that it costs 0 credits, and mentions authentication requirements, which are not covered by annotations. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose in the first sentence, followed by technical and authentication details. Every sentence adds value (endpoint, cost, auth requirement) with no redundant information. It is efficiently structured and appropriately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (0 parameters, no output schema) and rich annotations, the description is mostly complete. It covers purpose, endpoint, cost, and authentication. However, it does not describe the return format (e.g., what data is included in the balance and deductions), which would be helpful since there is no output schema. This minor gap prevents a perfect score.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, maintaining focus on the tool's purpose and behavior. This meets the baseline of 4 for zero parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('Check the remaining credit balance and recent deductions') and resource ('authenticated SocialCrawl account'), distinguishing it from siblings like socialcrawl_get_docs or socialcrawl_request. It provides a complete picture of what the tool does beyond just the title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool ('Check the remaining credit balance and recent deductions') and mentions the prerequisite ('Requires a valid SOCIALCRAWL_API_KEY'), but does not provide guidance on when not to use it or name specific alternatives among the sibling tools. This gives clear context without exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.