Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Rhylthyme

REMOTE · MCP.RHYLTHYME.COM

Real-time multi-track schedules for cooking, lab protocols, events and workouts. Validate and share.

0 this week 82 Trust /100

Last scanned (21 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Workflow Automation

Recent critical change

Authorization (26 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3454 tokens (~115/item across 30 items; 20 tools + 10 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
  • Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 10 Nov 26 0
    • Tool “import_from_source” rewrote its description, which is the text the model reads security
    • “import_from_source” reworded the description of “text” cosmetic
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 0
    • New tool “publish_timeline_image”, which the server declares destructive security
    • Tool “preview_timeline” rewrote its description, which is the text the model reads security
    • Tool “preview_timeline” no longer declares itself destructive security
  • 19 Oct 26 0
    • Tool “import_from_source” rewrote its description, which is the text the model reads security
    • “import_from_source” reworded the description of “text” cosmetic
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
  • 14 Oct 26 0
    • Tool “import_from_source” rewrote its description, which is the text the model reads security
    • “import_from_source” reworded the description of “text” cosmetic
  • 11 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.rhylthyme.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.rhylthyme.com CN=YR2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 RSA 2048 SHA256-RSA 6bf3c3a7b3fcbc04f72c884d25969fd0ec8
SANs: *.rhylthyme.com, rhylthyme.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.rhylthyme.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
rhylthyme.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net https://unpkg.com https://www.googletagmanager.com https://www.google-analytics.com https://googleads.g.doubleclick.net; style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com https://cdn.jsdelivr.net; font-src 'self' https://cdnjs.cloudflare.com; img-src 'self' data: https: blob:; connect-src 'self' https://api.anthropic.com https://pbqudpgkfhultuoqibem.supabase.co https://*.supabase.co https://www.google-analytics.com https://www.googletagmanager.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://www.google.com; frame-src 'self' https://www.googletagmanager.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.rhylthyme.com/mcp Verified 200
http (plaintext) http://mcp.rhylthyme.com/mcp HTTPS enforced 308 https://mcp.rhylthyme.com/mcp
MCP tools · 20 exposed · ~2,489 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_schedule ~301

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 track. Pass finishAt to answer 'when do I start X so everything is ready at 6pm?'. Pure computation. With `history` (run records) or `program_id` it also predicts durations from recorded runs.

NameTypeReqDescription
finishAtstring–ISO 8601 datetime everything must END at, e.g. '2026-11-26T18:00:00-05:00'. Start times are worked backwards from it.
historyarray–Recorded runs of this program (from load_run); adds predicted durations.
predictionContextobject–Optional: environmentId, userTags (variance factors), userId, programVersion, minIdentical, minModel, corrThreshold, verdicts. See rhylthyme://guide/tools.
programobjectyesProgram JSON; shape under validate_program.
program_idstring–Saved program UUID: loads the user's own recorded runs as the history.
startAtstring–ISO 8601 start datetime. Ignored with finishAt.
tokenstring–Access token from the login tool. Omit when the account is connected.
useDurationsstring–planned (default): analyse the program as authored. predicted: as the history says it will run.
NameTypeReqDescription
actorPeakobjectyes–
bindingConstraintsarray––
criticalPatharrayyes–
durationsUsedstring––
inFlightarray––
makespanstringyes–
makespanSecondsnumberyes–
name–yes–
plannedMakespanstring––
plannedMakespanSecondsnumber––
predictedCriticalPatharray––
predictedMakespanstring––
predictedMakespanSecondsnumber––
programId–yes–
resourceConflictsarrayyes–
stepsarrayyes–
tracksarrayyes–
validationobject––
wallClock–yes–

No examples provided.

calibrate_program ~216

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 author's, with the evidence per step and the effect on total length. Saves nothing; with `accept` it returns the calibrated program. Needs the user's Rhylthyme account.

NameTypeReqDescription
accept––Step ids to accept, or "all": also returns the calibrated program. Nothing is saved either way.
historyarray–Run records to use instead of the stored ones.
kinteger–Measurements a step needs for a proposal (default 5).
programobject–Program JSON to calibrate; omit to use program_id's saved JSON.
program_idstring–Saved program UUID whose recorded runs are the evidence.
sincestring–Only runs started on or after this date (YYYY-MM-DD or ISO).
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

create_environment ~93

Describe a workspace's equipment limits (one oven, two centrifuges, one stage) as resourceConstraints to copy into a program, so steps that share equipment are scheduled around each other.

NameTypeReqDescription
actorsinteger–How many people can work at once (default 1).
descriptionstring––
namestringyes–
resourceConstraintsarrayyes–
typestringyes–

No output schema declared.

No examples provided.

get_renderer_source ~57

Return the open-source timeline renderer's JavaScript (Apache-2.0, about 90 KB, no dependencies) for an HTML page or artifact that cannot load external scripts; it defines Rhylthyme.renderTimeline(container, program).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_from_source ~228

Import a recipe, protocol or run of show into a program. source: spoonacular, themealdb (recipes); protocolsio, opentrons, benchling (lab); cooklang (.cook URL); ontime (run of show). action: search (no account needed), import (query = URL or id), random. import, random and benchling need the user's Rhylthyme account. `enrich: true` splits an import into parallel tracks. Returns the program.

NameTypeReqDescription
actionstringyes–
enrichboolean–With action='import': split the import into parallel tracks with cross-track triggers. One model call, capped per day.
querystring–Keywords (search), or the URL or id (import).
sourcestringyes–
textstring–Pasted source instead of a URL: an Opentrons .py, or an Ontime project JSON or rundown table (CSV, TSV or Markdown).
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

import_text ~184

Turn pasted text (a recipe, protocol, run sheet or training plan) into a validated multi-track program on the server, in four model turns, with a table of the source span each step came from. Capped per day. Needs the user's Rhylthyme account.

NameTypeReqDescription
deadlinestring–When everything must be finished, if the user said: '18:00', 'dinner at six', an ISO datetime.
environmentTypestringyeskitchen, lab, events, gym or generic.
hintsstring–Equipment and people limits in the user's words, e.g. 'one oven, two burners, one cook'.
textstringyesThe source text, all of it, as the user wrote or pasted it.
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

list_my_programs ~46

List the user's saved programs. Needs the user's Rhylthyme account.

NameTypeReqDescription
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

list_public_runs ~112

List anonymous runs other people contributed for one exact program version: actual against planned length, and their conditions. For 'how long does this really take?'. No account needed. Takes `program` or `program_hash`.

NameTypeReqDescription
limitinteger–Runs to return, newest first (default 50).
programobject–Program JSON to look up instead; hashed here.
program_hashstring–Program hash, 'sha256:' + 64 hex (a run record's programVersion).

No output schema declared.

No examples provided.

list_runs ~83

List recorded runs of a saved program: when, how it ended, actual against planned length. For 'how long did this take last time?'. Needs the user's Rhylthyme account.

NameTypeReqDescription
program_idstringyesProgram UUID from list_my_programs.
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

load_program ~70

Open one of the user's saved programs by id: summary plus live-timeline URL. Needs the user's Rhylthyme account.

NameTypeReqDescription
program_idstringyesProgram UUID from list_my_programs.
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

load_public_recipe ~40

Open a public catalog entry by id: summary plus live-timeline URL.

NameTypeReqDescription
program_idstringyesProgram UUID (from search_public_recipes)

No output schema declared.

No examples provided.

load_run ~77

Open one recorded run: planned against actual timing per step, what ended each step, pauses. Shows where a plan drifts. Needs the user's Rhylthyme account.

NameTypeReqDescription
run_idstringyesRun UUID from list_runs.
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

login ~82

For apps that cannot connect the Rhylthyme account directly: returns a sign-in URL, then accepts the pasted token. Only the user's own saved programs, runs and imports need it; everything public works without. Tokens last about an hour.

NameTypeReqDescription
tokenstring–The token from the login page. Leave empty on the first call to get the sign-in URL.

No output schema declared.

No examples provided.

preview_timeline ~105

Return a static Gantt image of a program with a caption, for 'show me a preview' or 'a picture of the timeline'. Publishes nothing. Planned versus actual: with `run` (a run record) it draws the actual bars over the plan.

NameTypeReqDescription
programobjectyesProgram JSON; shape under validate_program.
runobject–A recorded run of the same program (the `run` object from load_run): draws planned versus actual.

No output schema declared.

No examples provided.

publish_timeline_image ~88

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 results or a person who wants a link to the picture. This puts a public copy of the program online that the person can't remove. Validates first and refuses an invalid program.

NameTypeReqDescription
programobjectyesProgram JSON; shape under validate_program.
NameTypeReqDescription
imageUrlstringyesPublic URL of the PNG.
shareIdstringyesThe public share's id.
urlstringyesPublic URL of the live timeline for the same share.

No examples provided.

review_program ~147

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 importer dropped, steps chained that could overlap, a total that disagrees with the source. Changes nothing; returns findings to show the user. Needs the user's Rhylthyme account.

NameTypeReqDescription
programobjectyesProgram JSON; shape under validate_program.
source_textstring–The source text (recipe, protocol), if you have it.
source_urlstring–Its URL, when the text is not to hand.
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

save_program ~72

Save a program to the user's account ('save this for later'); the same programId updates it. Needs the user's Rhylthyme account.

NameTypeReqDescription
programobjectyesProgram JSON; shape under validate_program.
tokenstring–Access token from the login tool. Omit when the account is connected.

No output schema declared.

No examples provided.

search_public_recipes ~87

Search the public catalog of recipes, lab protocols, event templates and workouts by name or keyword. Returns ids, names, descriptions and URLs; no account needed.

NameTypeReqDescription
environmentstring–Which catalog: kitchen (default), laboratory, event or gym.
limitinteger––
querystring–Keyword; matches name and description. Empty returns the newest entries.
NameTypeReqDescription
countnumberyes–
environment–yes–
querystringyes–
resultsarrayyes–

No examples provided.

validate_program ~285

Check a program before publishing or saving it: ids, dangling or cyclic triggers, steps overlapping in a track, tasks with no resourceConstraint, durations, replicates/instances misuse. Every finding has a code, a message and a suggested fix. Pure computation.

NameTypeReqDescription
programobjectyesProgram JSON: {programId, name, environmentType?, actors?, tracks: [{trackId, name, steps: [{stepId (unique program-wide), name, task?, duration, startTrigger, replicates?, choice?}]}], resourceConst…
NameTypeReqDescription
errorsarrayyes–
infoarray––
stats–yes–
validbooleanyes–
warningsarrayyes–

No examples provided.

visualize_schedule ~116

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 schedule the user wants to follow or share ('plan this so it all finishes at 6', 'when do I start each thing'). Validates first and refuses an invalid program with fix hints.

NameTypeReqDescription
allowInvalidboolean–Publish despite validation errors. Only when the user explicitly wants an imperfect draft shared.
programobjectyesProgram JSON; shape under validate_program.
NameTypeReqDescription
imageUrl–yes–
makespanSecondsnumberyes–
shareId–yes–
urlstringyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Rhylthyme MCP server?

Rhylthyme is a hosted endpoint at https://mcp.rhylthyme.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.rhylthyme.com

# add to Claude Code
claude mcp add --transport http com-rhylthyme-rhylthyme 'https://mcp.rhylthyme.com/mcp'
Common questions

What is the Rhylthyme MCP server?

Rhylthyme is an MCP server listed in the public MCP registry as com.rhylthyme/rhylthyme. Real-time multi-track schedules for cooking, lab protocols, events and workouts. Validate and share. This page covers its hosted endpoint (https://mcp.rhylthyme.com/mcp).

Is the Rhylthyme MCP server safe to use?

Rhylthyme scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Rhylthyme MCP server expose?

Rhylthyme exposes 20 tools: validate_program, analyze_schedule, visualize_schedule, import_from_source, import_text, and 15 more. Their descriptions and schemas cost roughly 2,489 tokens of context every time the server is loaded.

Does the Rhylthyme MCP server require authentication?

No. We connected to Rhylthyme without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Rhylthyme MCP server still maintained?

Rhylthyme is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Rhylthyme MCP server?

VerifyMCP ran 13 checks on Rhylthyme, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.