_ registry / mcp streamable-http · checked 17m ago

runlater

https://runlater.app

Registry code: 06c10b76d1e7f328

api record

RunLater sends HTTP requests later: once at an exact time, or on a cron schedule, with retries and a log of every run.

Use schedule_request to create one (url plus run_at for one time, or cron for recurring; give a timezone when the person names a local time). Use list_schedules and get_schedule to check on them; get_schedule includes recent runs with status codes and responses. pause_schedule, resume_schedule, run_now and delete_schedule act on one schedule by id.

endpoint
https://runlater.app/api/mcp
protocol
streamable-http ·2025-06-18
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 runlater live?
Yes — it answered the hub's last check (checked 17m ago). It answered 100% of checks over the last 30 days.
Is runlater free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does runlater have?
8 tools: schedule_request, pause_schedule, resume_schedule, account_status, delete_schedule, list_schedules, get_schedule, run_now.
Is runlater 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
100%

90 days 100%· all time 100%

latency
290ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

_ what it can do 8 tools
8 auth-required 8 of 8 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.

  • schedule_request auth-required never probed

    Schedule an HTTP request to a public URL: once at an exact time (run_at) or repeatedly (cron). Pass exactly one of run_at or cron. RunLater sends it, retries failures and logs every run. Returns the schedule with its id and next run time.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "maxLength": 2048,
      "description": "Public http(s) URL to call. Private and local addresses are refused."
    },
    "body": {
      "type": "string",
      "maxLength": 65536,
      "description": "Request body as text (JSON goes here as a string). Not sent on GET or DELETE."
    },
    "cron": {
      "type": "string",
      "maxLength": 200,
      "description": "Recurring: 5-field cron (minute hour day-of-month month day-of-week), for example \"0 9 * * 1\" for Mondays at 9:00. At most once a minute."
    },
    "name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Short label shown in the dashboard. Default: method and host."
    },
    "method": {
      "enum": [
        "GET",
        "POST",
        "PUT",
        "PATCH",
        "DELETE"
      ],
      "type": "string",
      "description": "HTTP method. Default POST."
    },
    "run_at": {
      "type": "string",
      "maxLength": 64,
      "description": "One-time: ISO date and time, for example 2026-12-01T09:00:00 (read in timezone) or 2026-12-01T15:00:00Z. At most two years ahead."
    },
    "headers": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "value"
        ],
        "properties": {
          "name": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "value": {
            "type": "string",
            "maxLength": 4000
          }
        }
      },
      "maxItems": 30,
      "description": "Request headers, for example [{\"name\":\"Authorization\",\"value\":\"Bearer abc\"}]. Values are never shown back."
    },
    "retries": {
      "type": "integer",
      "maximum": 10,
      "minimum": 0,
      "description": "Retries after a failed attempt, with exponential backoff. Default 3."
    },
    "timezone": {
      "type": "string",
      "maxLength": 64,
      "description": "IANA time zone for run_at without an offset and for cron, for example America/New_York. Default UTC."
    },
    "timeout_seconds": {
      "type": "integer",
      "maximum": 300,
      "minimum": 1,
      "description": "Seconds to wait for a response. Default 30."
    }
  }
}
    arguments 87 lines
  • pause_schedule auth-required never probed

    Pause a scheduled request so it stops running until resumed.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Schedule id, from schedule_request or list_schedules"
    }
  }
}
    arguments 15 lines
  • resume_schedule auth-required never probed

    Resume a paused request. A recurring one continues at its next cron time. A one-time one needs its run time to still be in the future.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Schedule id, from schedule_request or list_schedules"
    }
  }
}
    arguments 15 lines
  • account_status auth-required 17m ago

    Show this workspace's plan, trial end date, limits and usage this month. With no plan yet, it includes the link where the 14-day trial starts.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • delete_schedule auth-required never probed

    Delete a scheduled request for good. It stops running and cannot be restored. To stop it for a while, use pause_schedule.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Schedule id, from schedule_request or list_schedules"
    }
  }
}
    arguments 15 lines
  • list_schedules auth-required 17m ago

    List scheduled requests in this workspace, newest first, with status (scheduled, paused or finished) and next run time.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Most to return. Default 50."
    },
    "status": {
      "enum": [
        "all",
        "scheduled",
        "paused",
        "finished"
      ],
      "type": "string",
      "description": "Filter by status. Default all."
    }
  }
}
    arguments 22 lines
  • get_schedule auth-required 17m ago

    Get one scheduled request with its recent runs: status code, duration, error and a preview of each response. Use this to check whether a request worked.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Schedule id, from schedule_request or list_schedules"
    },
    "runs": {
      "type": "integer",
      "maximum": 100,
      "minimum": 0,
      "description": "How many recent runs to include. Default 10."
    }
  }
}
    arguments 21 lines
  • run_now auth-required never probed

    Send a scheduled request once, right now, without retries, and return the status code and response. A successful run counts toward the monthly limit. A one-time request is finished after this.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Schedule id, from schedule_request or list_schedules"
    }
  }
}
    arguments 15 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 06c10b76d1e7f328.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/06c10b76d1e7f328/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/06c10b76d1e7f328/badge.svg)](https://brick.blue/agent/06c10b76d1e7f328?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.