Skip to main content
Glama

Seo Competitors

Server Details

SEO Competitors MCP — domain ranked keywords via DataForSEO Labs (dataforseo.com)

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
31.5% over 39 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-seo-competitors
GitHub Stars
0
Server Listing
mcp-seo-competitors

TDQS

A3.9/5.0

Scored across 32 tools

Disambiguation3/5

Most tools carve out genuinely distinct niches (bet_research vs polymarket_edges vs polymarket_arbitrage vs polymarket_fill_risk vs polymarket_kalshi_spread), and the descriptions work hard to draw boundaries. But ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are three nearly-identical universal routers — the beta one is explicitly a duplicate right now — and discover_tools/suggest_questions both answer 'what can I ask?'. These overlaps force the agent to guess which near-equivalent entry point to pick.

Naming Consistency4/5

Everything uses snake_case, with clear verb_noun forms (resolve_entity, compare_entities, list_subscriptions, validate_claim, generate_llms_txt) alongside clean bare verbs (remember, recall, forget, subscribe, unsubscribe) and consistent namespacing (ask_pipeworx*, polymarket_*, pipeworx_*). Only minor deviation is a few noun-first names like entity_profile, bet_research, and ai_visibility_check, which stay readable and on-pattern.

Tool Count2/5

32 tools is heavy and the surface sprawls well beyond what a server named 'Seo Competitors' implies, with only four tools actually being SEO-related. The bulk is a broad data gateway, so the count reflects a general-purpose toolkit rather than a focused, well-scoped set.

Completeness4/5

Judged as the gateway it actually is, coverage is strong: routing, grounded answers, entity resolution, comparison, profiles, change feeds, a full prediction-market suite with fill-risk and decay tracking, subscriptions, memory, and discovery are all present with few dead ends. The gap is against the stated name — SEO coverage is thin (no backlink, SERP-tracking, or keyword-research tools beyond seo_domain_ranked_keywords).

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."
  2. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
        -  "company"
        -]New value: +[
        +  "company",
        +  "ticker"
        +]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  3. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

  • F
    license
    C
    quality
    D
    maintenance
    MCP server for Keys.so SEO API, enabling domain and keyword analysis, competitor research, and SEO metrics retrieval through natural language.
    151
    4
    -
  • 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
    34 npm
    39
    MIT
  • 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
    880 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    SEO Intelligence MCP Server — 13 tools for keyword research, SERP analysis, domain audits, competitor gaps, on-page optimization. Part of ToolOracle (tooloracle.io).
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.