Skip to main content
Glama
Sign In
inwx-mcp

inwx-mcp

by SilentFuture
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to inwx-mcp

No user-submitted related servers found.

    Related Servers

    • netcup-mcp

      twink0r
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes the CCP domain webservice as MCP tools, enabling an agent to list domains, read and edit DNS zones, manage contact handles, and handle domain transfers and registration across multiple accounts with cached, isolated sessions.
      2
      MIT
    • nameai-mcp

      nameai-mcpofficial

      namekart
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables domain search and availability checks, WHOIS lookups, TLD registration pricing, and TLD requirement queries through MCP tools.
      -

    • MCP Namecheap Server

      johnsorrentino
      A
      license
      B
      quality
      D
      maintenance
      Provides integration with the Namecheap API for domain management operations, including domain listing, availability checks, and nameserver configuration. It allows users to interact with their Namecheap account through natural language commands in MCP-compatible clients.
      3
      20 npm
      20
      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

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource-and-action pair: account, domain, contact, nameserver, or raw API access. List vs. detail vs. write vs. read-only operations are clearly separated, so an agent should not easily confuse them.

    Naming Consistency5/5

    Tool names follow a consistent resource_action snake_case pattern, e.g. domain_list, domain_info, domain_renew, contact_create, nameserver_list. The only generic name, api_call, is intentionally presented as an expert fallback, not as part of the normal naming pattern.

    Tool Count5/5

    15 tools is at the upper bound of the ideal range, but each covers a necessary INWX domain-management concern: account, domains, contacts, nameservers, and raw API access. There is no obvious padding, and the scope is coherent.

    Completeness3/5

    The named tools cover reads plus domain transfer/update/renew and contact create, but miss high-level contact update/delete, domain registration, and nameserver zone modifications. The api_call escape hatch makes those operations possible, but only through raw low-level API calls.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources