Skip to main content
Glama
k2spam

timeweb-mcp

by k2spam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to timeweb-mcp

No user-submitted related servers found.

    Related Servers

    • selectel-mcp

      a-slvn
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives an AI agent controlled access to a Selectel cloud account: OpenStack cloud servers, S3 object storage, and account billing.
      1
      MIT

    • amoCRM MCP Server

      DocAtWork2026
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for amoCRM integration, enabling AI assistants to manage leads, contacts, companies, tasks, and more via natural language.
      4
      MIT

    • linux-ssh-mcp

      JINDEZHIDIYE
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.
      MIT

    • MCP VKUSVILL

      Bazilio-san
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for integrating AI assistants with VkusVill services, allowing natural language access to VkusVill data and operations.
      1
      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.7/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: domains, DNS records, servers, server power, diagnostics, SSH, services, and account info are clearly separated. There is no overlap between tools like server_power, service_control, and ssh_exec because they operate at different levels (hardware, systemd, arbitrary commands).

    Naming Consistency4/5

    The majority of tools follow a consistent verb_noun pattern (list_domains, create_dns_record, get_server). A few deviate with noun_verb or noun_noun forms like server_power, server_diagnostics, account_status, and service_control, but the naming remains readable and predictable overall.

    Tool Count4/5

    20 tools is slightly above the ideal 3-15 range but is justified for a cloud provider API that covers servers, domains, DNS, and account management. The count is well-scoped and each tool serves a clear purpose without redundancy.

    Completeness4/5

    The tool surface covers full CRUD for DNS records and core lifecycle for servers (create, delete, list, get, power, logs, diagnostics, SSH, service control). Minor gaps exist such as no domain create/delete or server update/resize, but agents can work around these for most common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources