Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
Directory / RunLater
RunLater
by runlater.app · https://runlater.app/api/mcp
Schedule HTTP requests from an agent: once at an exact time or on cron, with retries and run logs.
Partial: 9 of 11 checks · 6 Nov 2026
At a glance
- Runs where
- On their server. What you send to it goes to them.
- What you need
- Nothing: it answered without a login
- Tools
- 9 tools
- Its own safety labels
- 3 read-only, 5 labeled as deleting or destroying, 1 labeled as changing things
- Memory it takes
- About 2,100 tokens of your AI's memory, just for its tool descriptions
- Tools that look alike
- 1 pair of tools with nearly the same description, so the AI may pick the wrong one
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 6 Nov 2026.
Is RunLater MCP server safe?
- None of the hidden-instruction wordings we know were found in its 9 tool descriptions.
- Its error messages showed no secrets or internal details.
- 3 of its 9 tools are labeled read-only; the others may change or send things.
- Overall it scored 84/100 on 6 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
- Its source code and packages.
- What a tool quietly does behind the scenes, such as writing a file or calling another service.
- Instructions hidden inside live tool answers. We only look for those in tool descriptions.
- Hidden instructions worded in a way our list doesn't know yet.
- Tools that could change something. Those are read, never run.
What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection
Known security advisories
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
9 tools, in the server's own words.
schedule_get_requestCreate one schedule that sends a GET to a public URL later: once at an exact time (run_at) or repeatedly (cron).
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).
list_schedulesread-onlyList scheduled requests in this workspace, newest first, with status (scheduled, paused or finished) and next run time.
get_scheduleread-onlyGet one scheduled request with its recent runs: status code, duration, error and a preview of each response.
pause_schedulePause a scheduled request so it stops running until resumed.
resume_scheduleResume a paused request.
run_nowSend a scheduled request once, right now, without retries, and return the status code and response.
delete_scheduleDelete a scheduled request for good.
account_statusread-onlyShow this workspace's plan, trial end date, limits and usage this month.
Test results
Safe mode: only tools labeled read-only were run. How the test works
- !Ready for the newest MCP versionnote
1 warning
- !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
- !Every tool is describednote
1 warning
- !schedule_get_request and schedule_send_request have nearly the same description (80% of their words are shared; the only difference: "get" vs "post", "put", "patch"), so an AI may not know which to pick
- ✓ConnectsConnected in 255 mspass
- ✓Lists its toolsFound 9 toolspass
- ✓Tools are labeled safe or dangerousEvery tool has a safety labelpass
- ✓No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.pass
- ✓Fast enoughpass
All good
- ✓Connecting took 255 ms
- ✓Listing tools took 52 ms
- ✓No secrets leakedChecked 6 error messages: no secrets or internal detailspass
- ✓Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guidepass
- –Tools work with good inputsnot tested
Not tested
- –list_schedules: Needs you to sign in, so it was not tested (not counted against the server)
- –get_schedule: Needs you to sign in, so it was not tested (not counted against the server)
- –account_status: Needs you to sign in, so it was not tested (not counted against the server)
- –schedule_get_request: Not run: labeled as changing data
- –schedule_send_request: Not run: labeled dangerous
- –pause_schedule: Not run: labeled dangerous
- –resume_schedule: Not run: labeled dangerous
- –run_now: Not run: labeled dangerous
- and 1 more
- –Bad inputs give a clean errornot tested
Not tested
- –list_schedules: Needs you to sign in, so bad inputs were not tested
- –get_schedule: Needs you to sign in, so bad inputs were not tested
- –Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)not tested
Test it yourself
Free and open source. Same checks, same score.
npx qamcp-cli https://runlater.app/api/mcpShow this score on GitHub
Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.
[](https://qamcp.dev/s/app-runlater-runlater.html)Score over time
- 6 Nov 202684
One test so far. New tests will show here.
Reviews
Coming soon: reviews from people who use RunLater, signed in with GitHub, one per person. Reviews never change the score.
QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.
Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works