Skip to main content
Glama
199-mcp

MCP Wait Timer Server

by 199-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP Wait Timer Server

No user-submitted related servers found.

    Related Servers

    • Sleep MCP Server

      Garoth
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides a simple sleep/wait tool, useful for adding delays between operations such as waiting between API calls or testing eventually consistent systems.
      1
      10 npm
      21
      ISC

    • mcp-wait

      lzientek
      A
      license
      A
      quality
      D
      maintenance
      A minimal MCP server that lets AI agents pause for a specified duration before resuming their workflow. Useful for polling patterns like waiting for PR approval or file creation.
      1
      2 npm
      MIT

    • mcp-wait

      AaLexUser
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a wait tool for AI agents to pause execution until a time duration elapses or a process terminates, useful for polling and waiting for builds/deployments.
      3 npm
      MIT

    • timer-mcp

      tharun52
      F
      license
      Not graded
      quality
      B
      maintenance
      A minimal MCP server that gives AI agents the ability to pause execution by waiting a specified number of seconds, with support for local and AWS AgentCore deployment.
      -

    • MCP-Wait

      automation-ai-labs
      A
      license
      B
      quality
      D
      maintenance
      A simple MCP server that provides waiting functionality to pause until other tasks finish, with progress reporting and support for CLI or HTTP server with SSE.
      1
      18 npm
      5
      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.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility for ambiguity or overlap between tools. The tool 'wait' has a single, clear purpose that cannot be confused with any other tool in this set.

    Naming Consistency5/5

    The naming is trivially consistent as there is only one tool. The tool name 'wait' follows a simple verb pattern, and there are no other tools to create inconsistency or mixed conventions.

    Tool Count2/5

    A single tool is too few for most server purposes, making the server feel thin and limited in scope. While a timer server might logically have few tools, one tool is borderline minimal and may not cover all expected timer-related operations, such as cancelling or listing waits.

    Completeness2/5

    The tool set is severely incomplete for a timer server. It only provides a wait function, missing obvious operations like cancelling an active wait, checking wait status, or managing multiple timers, which are common in timer-related domains.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources