Skip to main content
Glama

Crontab

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Crontab expression MCP.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
45.7% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-crontab
GitHub Stars
0
Server Listing
mcp-crontab

TDQS

A3.8/5.0

Scored across 33 tools

Disambiguation3/5

Descriptions are unusually explicit about when to use each tool, but the set contains several near-duplicates (ask_pipeworx vs ask_pipeworx_beta, which is admitted to currently match exactly; ask_pipeworx vs ask_pipeworx_grounded vs deep_research; ai_visibility_check vs scan_competitor_ai_presence) and overlapping meta-tools (discover_tools vs suggest_questions). An agent can usually pick correctly by reading, but boundaries are fuzzy in places.

Naming Consistency4/5

All tool names use consistent snake_case and most follow a predictable prefix/domain scheme (ask_pipeworx*, polymarket_*, pipeworx_*, scan_*). It is not a uniform verb_noun pattern (e.g., deep_research, entity_profile, recent_changes are noun/adjective forms), but casing and readability are consistent throughout.

Tool Count2/5

33 tools is heavy and spans many unrelated domains (cron parsing, memory, subscriptions, Polymarket betting, AI visibility, npm dependency scanning, llms.txt generation, and a general data gateway). The stated server purpose of 'Crontab' is nowhere near a 33-tool surface, so most tools feel scoped to a different server.

Completeness3/5

Some sub-surfaces are complete (remember/recall/forget; subscribe/unsubscribe/list_subscriptions/recent_alerts), and the data-gateway coverage is broad via proxy tools. However the apparent Crontab purpose only has describe_cron and next_runs with no way to create, update, or manage cron jobs, a notable lifecycle gap.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

  • cronmcp

    vaibhavpandeyvpz
    A
    license
    Not graded
    quality
    D
    maintenance
    Cron scheduler stdio MCP server that enables creating and managing scheduled prompt jobs with persistence and optional tick notifications.
    11 npm
    3
    MIT

  • croncron

    itsnotrwanman
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that lets AI agents manage cron jobs through natural language — adding, listing, pausing, removing, running, and viewing logs of scheduled jobs with plain-English schedule parsing, automatic log capture, missed-run detection, and failure alerts.
    MIT

  • Claude Runner MCP

    floriansmeyers
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server for scheduling and executing Claude Code CLI tasks via cron expressions, featuring a web dashboard and webhook support. It enables users to dynamically create custom MCP servers, manage recurring AI jobs, and track execution history with token and cost analytics.
    24
    MIT
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources