Skip to main content
Glama
spidra-io

spidra-mcp-server

Official
by spidra-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to spidra-mcp-server

No user-submitted related servers found.

    Related Servers

    • browser-use-mcp

      ellllapie
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to browse websites, extract information, fill forms, interact with pages, and execute multi-step web tasks autonomously.
      -

    • Crawl4AI RAG MCP Server

      Chillbruhhh
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents and coding assistants with advanced web crawling and RAG capabilities, allowing them to scrape websites and leverage that knowledge through various retrieval strategies.
      2
      MIT

    • Crawl4AI RAG MCP Server

      Rob-P-Smith
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to crawl websites, extract and store web content with semantic search capabilities using vector embeddings, and retrieve information through natural language queries with tag-based filtering and intelligent content cleaning.
      -

    • Crawlberg MCP Server

      xberg-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to crawl and scrape websites, converting HTML to clean Markdown and structured metadata with support for JavaScript rendering, bot evasion, and SSRF protection.
      174
      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

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scrape (single combined), batch_scrape (parallel independent), crawl (discovery), with separate status/cancel tools per job type. The descriptions explicitly contrast spidra_scrape vs spidra_batch_scrape vs spidra_crawl, eliminating ambiguity.

    Naming Consistency4/5

    All tools share the 'spidra_' prefix and mostly follow a verb_noun pattern (check_scrape_status, cancel_batch, crawl_pages). Minor deviations like 'spidra_usage' (pure noun) and 'spidra_crawl_extract' (slightly awkward compound) prevent a perfect score, but the overall convention is predictable.

    Tool Count5/5

    12 tools is well-scoped for a scraping/crawling server. Each tool covers a specific action (start, poll, cancel, inspect) for each operation type (scrape, batch, crawl), plus logs and usage monitoring. No redundant or superfluous tools.

    Completeness4/5

    The toolset covers the full lifecycle for batch and crawl jobs (create, status check, cancel, retrieve results), plus logs and usage. Minor gaps: no explicit cancel for a single long-running scrape, and retry of failed items is only available via dashboard, not API. Core workflows are otherwise complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources