Skip to main content
Glama
abukreev-dev

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to keyso-mcp

No user-submitted related servers found.

    Related Servers

    • keysso-mcp

      zai-one
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to retrieve keyword, competitor, and advertising data from Keys.so SEO reports through the MCP server.
      1
      -

    • Mangools MCP

      marwa-mrwan
      F
      license
      C
      quality
      C
      maintenance
      Standalone MCP server for the Mangools API with 82 tools covering keyword research, SERP analysis, rank tracking, backlinks, competitor research, and AI search visibility. Enables natural language interaction with Mangools SEO capabilities.
      82
      -

    • SEO AI Assistant

      ayushsinghvi92
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI assistants to perform SEO automation tasks including keyword research, SERP analysis, and competitor analysis through Google Ads API integration.
      1
      -

    • Haloscan MCP Server

      Cryptoptimiste
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that integrates with the Haloscan SEO API to provide tools for keyword research, SERP analysis, and domain performance tracking. It enables users to perform comprehensive SEO tasks, including competitor analysis and visibility monitoring, within MCP-compatible clients.
      33
      190 npm
      1
      MIT

    • Semrush MCP

      mrkooblu
      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
      311 npm
      39
      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

    C2.2/5.0

    Scored across 151 tools

    Disambiguation1/5

    With 151 tools, many have overlapping purposes (e.g., multiple 'organic keywords' variants for simple vs. group reports). Auto-generated hash suffixes like 'sitepag_586cf11f' make tools indistinguishable, and a universal keyso_api_request tool further blurs boundaries.

    Naming Consistency2/5

    The dominant pattern is keyso_{http_method}_{url_path_with_underscores}, which is somewhat consistent. However, the pattern is broken by arbitrary hash suffixes, inconsistent use of '_uid'/'_rid'/'_id' appendages, and the outlier keyso_api_request.

    Tool Count1/5

    151 tools is an extreme count for an MCP server, overwhelming any agent's ability to select the right one. This is an entire API surface dumped into the tool namespace rather than a curated set.

    Completeness3/5

    The server covers a broad domain (reports, SERP, Wordstat, monitoring, AI tracker, Zen, links, projects) with many create/state/result triads. However, some areas lack obvious update/delete operations, and the presence of a catch-all API request tool suggests gaps in the structured surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources