Skip to main content
Glama
scalably-io

io.scalably/dataforseo-mcp

Official
by scalably-io

Related Servers

Alternatives to io.scalably/dataforseo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Model Context Protocol (MCP) server implementation for DataForSEO, enabling AI assistants to interact with selected DataForSEO APIs and obtain SEO data through a standardized interface.
      89
      7,607 npm
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP hosts to access 22 SEO Intellect API tools, handling task submission, polling, and retrieval for SEO analysis workflows.
      22
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      MCP server & CLI for keyword research, domain analytics, backlinks, traffic analysis, and competitive intelligence using Semrush API data.
      77
      46 npm
      39
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct: api_request handles API calls, docs_search fetches specific documentation pages, docs_index retrieves the documentation index, and docs_list_sections lists section names. However, docs_search and docs_index could be confused since both retrieve documentation-related content, though their purposes differ enough to avoid significant ambiguity.

    Naming Consistency3/5

    Three tools share a consistent 'docs_' prefix with verb-noun style (docs_search, docs_index, docs_list_sections), but api_request breaks the pattern and uses a noun-noun construction. The naming is readable but not fully uniform, mixing conventions.

    Tool Count5/5

    Four tools is an ideal size for a focused server that combines documentation retrieval with API request execution. Each tool has a clear purpose, and the count feels neither sparse nor bloated for the server's stated scope.

    Completeness5/5

    The tool set covers the full workflow: discovering available sections (docs_list_sections), browsing the index (docs_index), fetching specific documentation (docs_search), and making authenticated API requests (api_request). No obvious dead ends or missing core operations are apparent for a documentation and API helper server.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues