MCP server for human-executed, resource-constrained schedules: validate, analyze
MCP server for human-executed, resource-constrained schedules: validate, analyze, import and publish live timelines on rhylthyme.com. Source of mcp.rhylthyme.com.
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://mcp.rhylthyme.com/mcp |
|---|---|
| Source | https://github.com/rhylthyme/rhylthyme-mcp |
| Transport | http |
| Tools | 20 |
| Auth | none |
| First seen | 2026-09-09 23:49:15 |
| Last checked | 2026-11-17 21:47:40 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 398 / 823 ms |
| Last successful check | 2026-11-17 21:47:40 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (20)
validate_program— Check a program before publishing or saving it: ids, dangling or cyclic triggers, steps overlapping in a track, tasks with no resourceConstranalyze_schedule— Put a program on the clock: each step's start and end, total length, the critical path and what gates it, resource conflicts, slack per tracvisualize_schedule— Publish a program as a live, shareable timeline (a public share link) and return its URL, with an ASCII Gantt and an itinerary. For a scheduimport_from_source— Import a recipe, protocol or run of show into a program. source: spoonacular, themealdb (recipes); protocolsio, opentrons, benchling (lab);import_text— Turn pasted text (a recipe, protocol, run sheet or training plan) into a validated multi-track program on the server, in four model turns, wcreate_environment— Describe a workspace's equipment limits (one oven, two centrifuges, one stage) as resourceConstraints to copy into a program, so steps thatlogin— For apps that cannot connect the Rhylthyme account directly: returns a sign-in URL, then accepts the pasted token. Only the user's own savedlist_my_programs— List the user's saved programs. Needs the user's Rhylthyme account.load_program— Open one of the user's saved programs by id: summary plus live-timeline URL. Needs the user's Rhylthyme account.list_runs— List recorded runs of a saved program: when, how it ended, actual against planned length. For 'how long did this take last time?'. Needs thereview_program— A model reads an imported program against its source and reports what looks wrong: a default duration on "simmer for an hour", a step the imload_run— Open one recorded run: planned against actual timing per step, what ended each step, pauses. Shows where a plan drifts. Needs the user's Rhycalibrate_program— Propose durations for a saved program from its recorded runs: median as the default, P10 to P90 as the range, at least as wide as the authorlist_public_runs— List anonymous runs other people contributed for one exact program version: actual against planned length, and their conditions. For 'how losearch_public_recipes— Search the public catalog of recipes, lab protocols, event templates and workouts by name or keyword. Returns ids, names, descriptions and Uload_public_recipe— Open a public catalog entry by id: summary plus live-timeline URL.save_program— Save a program to the user's account ('save this for later'); the same programId updates it. Needs the user's Rhylthyme account.preview_timeline— Return a static Gantt image of a program with a caption, for 'show me a preview' or 'a picture of the timeline'. Publishes nothing. Plannedpublish_timeline_image— Publish a program's static Gantt image at a public share link and return the image URL, for a client that can't display images in tool resulget_renderer_source— Return the open-source timeline renderer's JavaScript (Apache-2.0, about 90 KB, no dependencies) for an HTML page or artifact that cannot lo
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:47:40 | ✓ | ✓ | 291 ms | 94 | active |
| 2026-11-17 21:32:35 | ✓ | ✓ | 351 ms | 90 | active |
| 2026-11-17 21:17:24 | ✓ | ✓ | 883 ms | 90 | active |
| 2026-11-17 21:02:23 | ✓ | ✓ | 402 ms | 90 | active |
| 2026-11-17 20:47:03 | ✓ | ✓ | 235 ms | 94 | active |
| 2026-11-17 20:32:01 | ✓ | ✓ | 326 ms | 90 | active |
| 2026-11-17 20:16:53 | ✓ | ✓ | 231 ms | 94 | active |
| 2026-11-17 20:01:14 | ✓ | ✓ | 227 ms | 94 | active |
| 2026-11-17 19:46:00 | ✓ | ✓ | 597 ms | 90 | active |
| 2026-11-17 19:30:52 | ✓ | ✓ | 271 ms | 94 | active |
| 2026-11-17 19:15:50 | ✓ | ✓ | 256 ms | 94 | active |
| 2026-11-17 18:59:56 | ✓ | ✓ | 471 ms | 90 | active |
| 2026-11-17 18:44:54 | ✓ | ✓ | 329 ms | 90 | active |
| 2026-11-17 18:29:53 | ✓ | ✓ | 429 ms | 90 | active |
| 2026-11-17 18:14:48 | ✓ | ✓ | 368 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.rhylthyme.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-rhylthyme-com-mcp # JSON