RunLater MCP server
app.runlater/runlaterrunlater.appstreamable-httpv1.1.0Scanned
Schedule HTTP requests from an agent: once at an exact time or on cron, with retries and run logs.
9 tools: 5 can delete or cancel things, 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RunLater MCP server can do
The RunLater MCP server is published by runlater.app, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (5 tools: schedule_send_request, pause_schedule, resume_schedule, run_now and 1 more) and create or change data (1 tool: schedule_get_request). 3 tools only read.
3 tools bring in text other people can write (schedule_get_request, schedule_send_request and run_now); 2 tools can send data out of your system (schedule_get_request and schedule_send_request).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Deletes or cancels 5Claude Code: deny
delete_scheduleDelete a scheduled request for good.No findings
Why it is in this group
- The name "delete_schedule" says "delete": a word for removing or ending something.
- The description says "cannot be restored".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a scheduled request for good. It stops running and cannot be restored.
Annotations the server declares
- title: Delete a schedule
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
pause_schedulePause a scheduled request so it stops running until resumed.No findings
Why it is in this group
- The name "pause_schedule" says "schedule": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Pause a scheduled request so it stops running until resumed.
Annotations the server declares
- title: Pause a schedule
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
resume_scheduleResume a paused request.No findings
Why it is in this group
- The name "resume_schedule" says "schedule": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Resume a schedule
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
run_nowSend a scheduled request once, right now, without retries, and return the status code and response.Reads text others writeNo findings
Why it is in this group
- The name "run_now" says "run": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Run a schedule now
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
schedule_send_requestCreate one schedule that sends a POST, PUT, PATCH or DELETE to a public URL later, with an optional body: once at an exact time (run_at) or repeatedly (cron).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "schedule_send_request" says "schedule": a word for a change.
- The name "schedule_send_request" also says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "schedule_send_request" says "send": it sends or publishes something to other people.
Description, as the server wrote it Create one schedule that sends a POST, PUT, PATCH or DELETE to a public URL later, with an optional body: once at an exact time (run_at) or repeatedly (cron). Pass exactly one of run_at or cron. Nothing is sent now. The URL is one the person supplies; RunLater does not limit it to a particular API. At the scheduled time RunLater sends it, which can change data at that URL, retries failures and logs every run. Returns the schedule with its id and next run time. Docs: https://runlater.app/docs/mcp
Annotations the server declares
- title: Schedule a POST, PUT, PATCH or DELETE request
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
schedule_get_requestCreate one schedule that sends a GET to a public URL later: once at an exact time (run_at) or repeatedly (cron).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "schedule_get_request" says "schedule": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Create one schedule that sends a GET to a public URL later: once at an exact time (run_at) or repeatedly (cron). Pass exactly one of run_at or cron. The URL is one the person supplies; RunLater does not limit it to a particular API. Nothing is sent now. RunLater sends it at the scheduled time, retries failures and logs every run. Returns the schedule with its id and next run time. Docs: https://runlater.app/docs/mcp
Annotations the server declares
- title: Schedule a GET request
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
account_statusShow this workspace's limits and usage this month.No findings
Why it is in this group
- The name "account_status" says "status": a word for reading.
Description, as the server wrote it Show this workspace's limits and usage this month. If it doesn't have access yet, the result says where to go next.
Annotations the server declares
- title: Account status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_scheduleGet one scheduled request with its recent runs: status code, duration, error and a preview of each response.No findings
Why it is in this group
- The name "get_schedule" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a schedule and its recent runs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_schedulesList scheduled requests in this workspace, newest first, with status (scheduled, paused or finished) and next run time.No findings
Why it is in this group
- The name "list_schedules" says "list": a word for reading.
Description, as the server wrote it List scheduled requests in this workspace, newest first, with status (scheduled, paused or finished) and next run time.
Annotations the server declares
- title: List scheduled requests
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:22 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://runlater.app/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://runlater.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (5 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://runlater.app/api/mcp: tools/list returned 9 tools to an anonymous client, including schedule_send_request (destructive), pause_schedule (destructive), resume_schedule (destructive), run_now (destructive), delete_schedule (destructive) and 1 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 5 to 6
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:account_statusOnly readsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
- Tools that change things, listed without credentials: 5 to 6
Tools2 added, 1 removed, 7 changed.+2 added−1 removed~7 changedView diff
- Added:schedule_get_requestChanges things
- Added:schedule_send_requestDeletes or cancels
- Removed:schedule_request
- Changed:account_statusOnly readsannotations
- Changed:delete_scheduleDeletes or cancelsdescriptioninputSchemaannotations
- Changed:get_scheduleOnly readsinputSchemaannotations
- Changed:list_schedulesOnly readsannotations
- Changed:pause_scheduleDeletes or cancelsinputSchemaannotations
- Changed:resume_scheduleDeletes or cancelsinputSchemaannotations
- Changed:run_nowDeletes or cancelsinputSchemaannotations
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http runlater https://runlater.app/api/mcpclaude mcp add --transport http runlater https://runlater.app/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__runlater__list_schedules",
"mcp__runlater__get_schedule",
"mcp__runlater__account_status"
],
"ask": [
"mcp__runlater__schedule_get_request"
],
"deny": [
"mcp__runlater__schedule_send_request",
"mcp__runlater__pause_schedule",
"mcp__runlater__resume_schedule",
"mcp__runlater__run_now",
"mcp__runlater__delete_schedule"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as runlater. Review it before you use it.
Capability tags behind 3 rules
- mcp__runlater__schedule_get_request untrusted-input, outbound
- mcp__runlater__schedule_send_request untrusted-input, outbound
- mcp__runlater__run_now untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.runlater/runlater/verify?hash=b93dd0631c209d09034b6781a22e443999242d2124eb1da02c74a10c047e248b" | jq -e '.changed == false'Pinned hash b93dd0631c20, from Nov 20, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.runlater/runlater/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.runlater/runlater)Source: MCP Registry. Synced Nov 6, 2026, 10:17 UTC.
RunLater MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RunLater MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RunLater MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: schedule_send_request, pause_schedule, resume_schedule, run_now and delete_schedule.
Can the RunLater MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the RunLater MCP server have?
- 9 tools: 5 destructive, 1 write, 3 read. schedule_send_request, pause_schedule, resume_schedule, run_now, delete_schedule, schedule_get_request, list_schedules, get_schedule and 1 more.
Does the RunLater MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RunLater MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): schedule_get_request and schedule_send_request.
Has the RunLater MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.