Skip to main content
Glama

x402-scraper

by io.github.ihen404
OverviewDiscussionsAdmin

Server Details

Autonomous HTTP 402 Web Scraping Mesh on Base for $0.02 USDC.

Ownership verified

The last two health checks of this connector failed. 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
8.9% over 44 days
Last Tested
Transport
Streamable HTTP
URL
Repository
ihen404/langchain-x402
GitHub Stars
0

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation4/5

The three tools are largely distinct: scrape handles a single URL, batch_scrape handles multiple URLs, and extract_metadata performs targeted selector extraction. The main overlap is between scrape and extract_metadata, since metadata extraction is arguably a mode of scraping, but the descriptions make the division reasonably clear.

Naming Consistency4/5

All names use snake_case with consistent verb-first style (scrape, batch_scrape, extract_metadata). The lone bare verb 'scrape' paired with the prefixed 'batch_scrape' is a minor stylistic deviation rather than an inconsistency.

Tool Count4/5

Three tools is on the lean side but each earns its place for a focused scraping server covering single, bulk, and targeted extraction cases. It sits just below a typical 5-15 range but is not thin enough to be a mismatch.

Completeness3/5

Core scraping needs are covered, but there is no crawl/link-following tool, no pagination or sitemap handling, and no output-format or storage options. These are notable gaps an agent would have to work around for larger scraping tasks.

Tool Schema Changelog

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

  1. 2 tool updates
    • Addedbatch_scrape
    • Addedextract_metadata
  2. 9 tool updates
    • Removedautomate
    • Removedcrawl
    • Removedextract
    • Removedget_analytics
    • Removedpdf
    • Removedrender
    • Addedscrape
    • Removedscreenshot
    • Removedsearch_rag
  3. 2 tool updates
    • Addedautomate
    • Addedget_analytics
  4. 1 tool update
    • Addedsearch_rag
  5. 5 tool updates
    • Changedcrawl1 field changed
      • addedInput schema / properties / maxPages
        Added value: +{
+  "description": "Maximum total pages to crawl",
+  "type": "number"
+}
    • Changedextract2 fields changed
      • addedInput schema / properties / selector
        Added value: +{
+  "description": "Optional CSS selector to target a specific container element",
+  "type": "string"
+}
      • addedInput schema / properties / timeout
        Added value: +{
+  "description": "Page load timeout in milliseconds",
+  "type": "number"
+}
    • Addedpdf
    • Changedrender1 field changed
      • addedInput schema / properties / waitForSelector
        Added value: +{
+  "description": "Optional CSS selector to wait for",
+  "type": "string"
+}
    • Addedscreenshot
  6. 4 tool updates
    • Addedcrawl
    • Addedextract
    • Addedrender
    • Removedscrape
  7. 1 tool update
    • First observedscrape

Related MCP Connectors

Related MCP Servers

Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources