Skip to main content
Glama
artgas1

xmlriver-mcp

by artgas1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to xmlriver-mcp

No user-submitted related servers found.

    Related Servers

    • yandex-mcp

      SvechaPVL
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Yandex Direct, Metrika, Wordstat, and Webmaster APIs, providing 132 tools to manage advertising campaigns, analytics, keyword research, and reporting through any MCP-compatible client.
      59
      MIT

    • Yandex Wordstat MCP

      N1arko
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying Yandex Wordstat via Yandex Cloud Search API. Enables checking phrase frequency, similar queries, regional demand, and seasonality trends.
      1
      MIT

    • G-Search MCP

      jae-jae
      A
      license
      B
      quality
      F
      maintenance
      A powerful MCP server that enables parallel Google searching with multiple keywords simultaneously, providing structured results while handling CAPTCHAs and simulating user browsing patterns.
      1
      49 npm
      274
      MIT

    • Yandex Webmaster MCP Server

      weselow
      A
      license
      C
      quality
      C
      maintenance
      MCP server that provides 46 tools for managing Yandex Webmaster API v4, enabling site management, sitemaps, indexing, search analytics, and more through natural language.
      46
      14 npm
      5
      MIT

    • io.github.dontsovcmc/yandex

      dontsovcmc
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Yandex Metrika API, enabling reporting, counter management, goals, filters, and other operations via natural language.
      12
      2
      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.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: URL indexation check, account management (balance, cost, tariff, tariff expiry), Google SERP parsing, Yandex Wordstat, Yandex SERP parsing, and Yandex Search API. There is no overlap or ambiguity.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (e.g., get_balance, check_url_indexed, google_search). All are snake_case with clear verbs, making the action predictable. The naming is uniform across the set.

    Tool Count5/5

    With 9 tools, the scope is well-calibrated: 4 tools cover account and cost management, and 5 cover search engine data access (Google, Yandex, indexation, keyword research). This is a complete yet focused surface for an SEO/SERP analysis tool.

    Completeness5/5

    The tool set covers all core operations expected from an XMLRiver client: account info (balance, tariff, cost, expiry), Google and Yandex search, URL indexation checking, and keyword frequency via Wordstat. There are no obvious gaps for the stated purpose of SEO and search data retrieval.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources