Skip to main content
Glama

Server Details

ScrapeCreators MCP — wraps the ScrapeCreators social-media + ad-library

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.2% over 25 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-scrapecreators
GitHub Stars
0
Server Listing
scrapecreators

TDQS

A3.8/5.0

Scored across 40 tools

Disambiguation2/5

Several clusters of tools overlap heavily, especially the ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research family and the large Polymarket analysis family. Although descriptions try to distinguish them, an agent still faces non-obvious choices between routing, grounding, and broad research tools.

Naming Consistency4/5

Names are overwhelmingly snake_case and mostly readable, with scrapecreators_* tools grouped by vendor prefix. There are minor deviations from a strict verb_noun pattern, since many are noun phrases rather than actions, but the convention itself is consistent.

Tool Count2/5

Forty tools is well above the 15-tool comfort zone and beyond the 25-tool threshold that suggests an overstuffed surface. The set spans unrelated domains like social scraping, prediction-market arbitrage, AI visibility, financial data, memory, and subscriptions, so the count feels excessive for a coherent server.

Completeness3/5

The overall surface is broad and includes CRUD-like coverage for subscriptions and memory, but there are notable gaps: descriptions reference polymarket_market and kalshi_market tools that are not exposed, and social scraping covers only a few platforms. These gaps are workable but will cause some agent dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
        +  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
        +  "type": "string"
        +}
      • addedOutput schema / properties / hint
        Added value: +{
        +  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
        +  "type": "string"
        +}
  2. 40 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedscrapecreators_facebook_ads
    • First observedscrapecreators_instagram_posts
    • First observedscrapecreators_tiktok_profile
    • First observedscrapecreators_youtube_channel
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    Provides unified access to social media data across nine networks (Instagram, TikTok, YouTube, etc.) through a set of MCP tools for profiles, posts, search, and comments, backed by the SocialBridge API.
    -
  • A
    license
    C
    quality
    A
    maintenance
    Hosted MCP server for 3,475 structured public web-data tools across 468 platform groups, returning clean JSON for search, maps, commerce, social, and finance.
    2
    500
    536 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for DataLikers — 51 tools for Instagram & TikTok data: Instagram user search by demographics (gender/age/race/country/city), profiles, engagement, posts, comments, hashtags, locations, stories, business accounts; TikTok users, videos, comments, hashtags, playlists. Local stdio via npx -y datalikers-mcp, requires only DATALIKERS_API_KEY.
    13 npm
    9
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables MCP clients to retrieve read-only public Instagram data through 27 tools covering profiles, posts, reels, stories, highlights, comments, likers, followers, hashtags, places, audio and keyword search. No login is required, and every response reports remaining API credits.
    27
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.