Skip to main content
Glama
OperatorNest

mcp-tools

by OperatorNest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-tools

No user-submitted related servers found.

    Related Servers

    • Cron Parser API

      Br0ski777
      A
      license
      Not graded
      quality
      D
      maintenance
      Parse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.
      1
      MIT

    • leftbrain

      Lazy-Coder-03
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides exact, deterministic tools for math, dates, units, validation, and more to AI agents, returning precise answers with explicit assumptions and warnings instead of model guesses.
      MIT

    • cronsense

      MrProLopstar
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to convert schedule text to cron expressions, describe cron in natural language, and compute upcoming run times.
      186 npm
      8
      MIT

    • Laplace's Hoard MCP Server

      Luissalet
      A
      license
      A
      quality
      B
      maintenance
      Enables language models and users to perform exact arithmetic, symbolic math, unit/date conversions, statistics, and read-only SQL queries over registered files, with every operation logged by a citable ID that humans can re-run.
      11
      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.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, and the descriptions explicitly cross-reference siblings (e.g., ai_api_cost vs. ai_subscription_stack_cost, meeting_time_zones vs. recurring_schedule vs. cron_next_runs). There is no meaningful overlap that would cause misselection.

    Naming Consistency5/5

    All names use consistent snake_case noun phrases (ai_api_cost, meeting_time_zones, recurring_schedule, ai_subscription_stack_cost, cron_next_runs). No mixed conventions or vague verbs appear.

    Tool Count5/5

    Five tools is well within the ideal 3–15 range, and each tool earns its place with a distinct capability. The set is neither bloated nor too thin for a utility server.

    Completeness4/5

    The surface covers AI cost estimation (API and subscriptions) and scheduling utilities (meeting overlap, recurring task plans, cron preview). Minor gaps exist, such as no holiday lookup or general time-zone conversion, but core workflows are complete and agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources