Skip to main content
Glama

Server Details

Crawlbase MCP — wraps the Crawlbase Crawling API (crawlbase.com, formerly

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
35.2% over 49 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-crawlbase
GitHub Stars
0
Server Listing
mcp-crawlbase

TDQS

A4/5.0

Scored across 34 tools

Disambiguation4/5

Most tools target distinct purposes, but the ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded trio overlaps heavily (beta currently identical to the base), and the six polymarket_* tools plus bet_research require close reading to separate. The long descriptions do provide strong disambiguation signals, so boundaries are mostly recoverable.

Naming Consistency3/5

Mostly snake_case, but conventions are mixed: some tools are verb_noun (compare_entities, resolve_entity, validate_claim), while many are noun-only or phrase-like (entity_profile, recent_changes, deep_research, bet_research, discover_tools). Vendored prefixes (crawlbase_, pipeworx_) are used inconsistently, adding to the lack of a single predictable pattern.

Tool Count2/5

34 tools is well above the 15-tool sweet spot and lands squarely in the 'too many' band, making the surface hard to scan and select from. The breadth (scraping, finance, polymarket, memory, subscriptions, meta) partially justifies it, but several clusters (ask_pipeworx variants, six polymarket tools) could be consolidated.

Completeness4/5

Coverage is broad and thoughtfully rounded: scraping (scrape/screenshot/structured), entity resolution and profiling, comparison, claim validation, memory CRUD (remember/recall/forget), and full subscription lifecycle (subscribe/unsubscribe/list/recent_alerts). Minor gaps exist in some sub-domains but graceful-degradation notes and explicit resolution contracts make the surface workable.

Tool Schema Changelog

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

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]New value: +[
        +  {
        +    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.