_ registry / mcp streamable-http · checked 5h ago

toolapi-cron

https://cron.toolapi.org

Registry code: c9fdf5c1a312183a

api record

Utility tools that parse, validate, describe and preview run times of 5-field cron expressions.

endpoint
https://cron.toolapi.org/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is toolapi-cron live?
Yes — it answered the hub's last check (checked 5h ago). It answered 99% of checks over the last 30 days.
Is toolapi-cron free to use?
Yes — the hub reached it with no key and no payment.
What tools does toolapi-cron have?
7 tools: cron_parse, cron_semantic_validate, cron_next_runs, cron_describe, cron_matches, cron_validate_batch, cron_validate.
Is toolapi-cron safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.7%

90 days 99.2%· all time 99.2%

latency
687ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 370 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
_ what it is for
topic
developer tools
used for
  • validate a cron expression
  • describe a cron expression in words
  • preview next cron run times
  • check if cron matches a datetime
takes → gives
text → text, data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • cron_parse reads unknown never probed

    Parse 5-field cron into named fields (minute hour dom month dow).

    mcp-tool

    {
  "type": "object",
  "required": [
    "expr"
  ],
  "properties": {
    "expr": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • cron_semantic_validate reads unknown never probed

    Validate cron field syntax and value ranges (minute 0-59, hour 0-23, etc.).

    mcp-tool

    {
  "type": "object",
  "required": [
    "expr"
  ],
  "properties": {
    "expr": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • cron_next_runs reads unknown never probed

    Preview next N execution times for a 5-field cron expression.

    mcp-tool

    {
  "type": "object",
  "required": [
    "expr"
  ],
  "properties": {
    "expr": {
      "type": "string"
    },
    "count": {
      "type": "integer",
      "default": 5,
      "maximum": 20,
      "minimum": 1
    },
    "timezone": {
      "type": "string",
      "default": "UTC"
    },
    "from_time": {
      "type": "string",
      "description": "Optional unix or ISO start time"
    }
  }
}
    arguments 25 lines
  • cron_describe reads unknown 21h ago

    Human-readable natural language description of cron expression (EN + ZH).

    mcp-tool

    {
  "type": "object",
  "required": [
    "expr"
  ],
  "properties": {
    "expr": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • cron_matches reads unknown never probed

    Check if a cron expression matches a specific datetime (ISO-8601).

    mcp-tool

    {
  "type": "object",
  "required": [
    "expr",
    "at_time"
  ],
  "properties": {
    "expr": {
      "type": "string"
    },
    "at_time": {
      "type": "string",
      "description": "ISO-8601 datetime"
    },
    "timezone": {
      "type": "string",
      "default": "UTC"
    }
  }
}
    arguments 20 lines
  • cron_validate_batch reads unknown never probed

    Batch semantic validate of 5-field cron expressions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "expressions"
  ],
  "properties": {
    "expressions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 30
    }
  }
}
    arguments 15 lines
  • cron_validate reads unknown never probed

    Check cron string has exactly five fields.

    mcp-tool

    {
  "type": "object",
  "required": [
    "expr"
  ],
  "properties": {
    "expr": {
      "type": "string"
    }
  }
}
    arguments 11 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c9fdf5c1a312183a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c9fdf5c1a312183a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c9fdf5c1a312183a/badge.svg)](https://brick.blue/agent/c9fdf5c1a312183a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on toolapi.org 6 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.