Skip to main content
Glama
bitterdev

scraper-api-mcp

by bitterdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to scraper-api-mcp

No user-submitted related servers found.

    Related Servers

    • Outscraper MCP Server by outscraper

      Outscraper MCP Serverofficial

      outscraper
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to Outscraper's data extraction services for business intelligence, location data, and reviews across platforms like Google Maps, Amazon, and Yelp. It enables AI assistants to perform comprehensive web scraping tasks including contact information retrieval and geolocation services.
      12 PyPI
      7
      MIT
    • Outscraper MCP by outscraper

      Outscraper MCPofficial

      outscraper
      A
      license
      B
      quality
      B
      maintenance
      Connects AI agents to Outscraper for business discovery, Google Maps intelligence, company and contact enrichment, review analysis, search, and structured web extraction.
      28
      260 npm
      4
      MIT

    • Facebook Scraper3 MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to the Facebook Scraper3 API to extract data from Facebook profiles, pages, groups, and the marketplace. It provides comprehensive tools for searching posts, people, and events, as well as retrieving detailed metadata for comments, reactions, and media.
      40
      1
      MIT

    • social-data-mcp

      mrocker
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve X/Twitter profiles and tweets, YouTube video and channel data, and TikTok profile and video stats on a pay-per-result basis without requiring login or platform API keys.
      33 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 84 tools

    Disambiguation4/5

    Tools are clearly grouped by platform with distinct resource-action suffixes, making it easy to distinguish between them. However, the large number of similar-looking Facebook stubs and versioned duplicates (v1 vs v2 Instagram) introduce minor ambiguity.

    Naming Consistency4/5

    The vast majority follow a consistent v{version}_{platform}_{resource}_{subresource} pattern, but a few outliers like account_credit_balance break the pattern, and mixing v1 and v2 adds slight inconsistency.

    Tool Count3/5

    84 tools is large for a single server, but each platform requires multiple endpoints. However, many are stub endpoints that provide mock data, reducing practical value and making the surface feel bloated.

    Completeness2/5

    Coverage is extensive for Instagram, YouTube, and Facebook, but notable gaps exist (e.g., no Twitter search, missing Spotify playlists, limited LinkedIn search). Many Facebook and Twitter endpoints are stubs, so the actual functionality is incomplete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources