Skip to main content
Glama
Sign In
scraper-api-mcp

scraper-api-mcp

by bitterdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to scraper-api-mcp

No user-submitted related servers found.

    Related Servers

    • Social Media Scraper

      Moore8455
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to extract profile data from LinkedIn, Facebook, and Instagram and to perform Google web searches through integrated APIs. It returns scraped results as JSON for use in AI workflows.
      -

    • Social Media Scraper - Custom

      ePolyakov344
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to retrieve LinkedIn, Facebook, and Instagram profile or company data and to perform Google web searches through exposed tools. It returns scraped information in JSON for easy reading in compatible clients.
      -

    • Social Media Scraper

      msasaki9002
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to scrape LinkedIn, Facebook, and Instagram profiles and perform Google searches through RapidAPI and Serper integrations, returning JSON-formatted data.
      -

    • Social Media Scraper

      Pinarf40751
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to retrieve public profile data from LinkedIn, Facebook, and Instagram and to perform Google searches via RapidAPI and Serper, returning structured JSON.
      -
    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

    ActivityInactive
    ResponsivenessOutdated data

    Resources