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.
      2
      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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: API cost estimation, subscription stack cost, meeting time zone calculation, recurring schedule estimation, and cron run preview. Descriptions explicitly differentiate the two cost tools (API vs subscriptions), and the time-related tools cover different aspects (meeting planning vs recurrence vs cron parsing). No overlap or confusion.

    Naming Consistency4/5

    All names use snake_case and are noun phrases, but prefix usage is inconsistent ('ai_' on two tools, absent on others) and pluralization varies ('zones', 'schedule', 'runs'). These are minor deviations from a fully predictable pattern, yet still readable and mostly consistent.

    Tool Count4/5

    Five tools falls within the reasonable range (3–15), but for a generically named 'mcp-tools' server the set feels under-scoped. Each tool is distinct, but the collection lacks a cohesive theme, making the count slightly low for the apparent breadth of the name.

    Completeness3/5

    The tools cover cost estimation and several time/schedule utilities, but they are independent with no shared domain. For a general-purpose toolkit, notable gaps exist (e.g., time zone conversion, calendar integration, broader scheduling operations), and no lifecycle coverage is present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources