Rhylthyme
REMOTE · MCP.RHYLTHYME.COM · SCANNED SEP 24
Real-time multi-track schedules for cooking, lab protocols, events and workouts. Validate and share.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 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 3397 tokens (~117/item across 29 items; 19 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 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 (21% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
claude mcp add --transport http com-rhylthyme-rhylthyme 'https://mcp.rhylthyme.com/mcp'
{
"mcpServers": {
"com-rhylthyme-rhylthyme": {
"url": "https://mcp.rhylthyme.com/mcp"
}
}
} {
"servers": {
"com-rhylthyme-rhylthyme": {
"type": "http",
"url": "https://mcp.rhylthyme.com/mcp"
}
}
} [mcp_servers.com-rhylthyme-rhylthyme] url = "https://mcp.rhylthyme.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-rhylthyme-rhylthyme": {
"type": "remote",
"url": "https://mcp.rhylthyme.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-rhylthyme-rhylthyme --url 'https://mcp.rhylthyme.com/mcp' --transport streamable-http
mcp_servers:
com-rhylthyme-rhylthyme:
url: "https://mcp.rhylthyme.com/mcp" {
"McpServers": {
"com-rhylthyme-rhylthyme": {
"Transport": "http",
"Url": "https://mcp.rhylthyme.com/mcp"
}
}
} assistant mcp add com-rhylthyme-rhylthyme -t streamable-http -u 'https://mcp.rhylthyme.com/mcp'
{
"mcpServers": {
"com-rhylthyme-rhylthyme": {
"type": "http",
"url": "https://mcp.rhylthyme.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 24 Sept 26 0
- New tool “review_program” functional
- “analyze_schedule” reworded the description of “history” cosmetic
- “analyze_schedule” reworded the description of “predictionContext” cosmetic
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “analyze_schedule” rewrote its description, which is the text the model reads security
- Tool “calibrate_program” rewrote its description, which is the text the model reads security
- Tool “load_program” rewrote its description, which is the text the model reads security
- Tool “create_environment” rewrote its description, which is the text the model reads security
- Tool “get_renderer_source” rewrote its description, which is the text the model reads security
- Tool “import_from_source” rewrote its description, which is the text the model reads security
- Tool “import_text” rewrote its description, which is the text the model reads security
- Tool “list_my_programs” rewrote its description, which is the text the model reads security
- Tool “list_public_runs” rewrote its description, which is the text the model reads security
- Tool “list_runs” rewrote its description, which is the text the model reads security
- Tool “load_public_recipe” rewrote its description, which is the text the model reads security
- Tool “load_run” rewrote its description, which is the text the model reads security
- Tool “login” rewrote its description, which is the text the model reads security
- Tool “preview_timeline” rewrote its description, which is the text the model reads security
- Tool “save_program” rewrote its description, which is the text the model reads security
- Tool “search_public_recipes” rewrote its description, which is the text the model reads security
- Tool “validate_program” rewrote its description, which is the text the model reads security
- Tool “visualize_schedule” rewrote its description, which is the text the model reads security
- Schema quality: 188 → 116 ▲ functional
- Destructive annotations: pass → 100 functional
- New resource “tool-guide” functional
- “analyze_schedule” reworded the description of “finishAt” cosmetic
- “analyze_schedule” reworded the description of “history” cosmetic
- “analyze_schedule” reworded the description of “predictionContext” cosmetic
- “analyze_schedule” reworded the description of “program” cosmetic
- “analyze_schedule” reworded the description of “program_id” cosmetic
- “analyze_schedule” reworded the description of “startAt” cosmetic
- “analyze_schedule” reworded the description of “token” cosmetic
- “analyze_schedule” reworded the description of “useDurations” cosmetic
- “calibrate_program” reworded the description of “accept” cosmetic
- “calibrate_program” reworded the description of “history” cosmetic
- “calibrate_program” reworded the description of “k” cosmetic
- “calibrate_program” reworded the description of “program” cosmetic
- “calibrate_program” reworded the description of “program_id” cosmetic
- “calibrate_program” reworded the description of “since” cosmetic
- “calibrate_program” reworded the description of “token” cosmetic
- “import_from_source” reworded the description of “enrich” cosmetic
- “import_from_source” reworded the description of “query” cosmetic
- “import_from_source” reworded the description of “text” cosmetic
- “import_from_source” reworded the description of “token” cosmetic
- “import_text” reworded the description of “deadline” cosmetic
- “import_text” reworded the description of “environmentType” cosmetic
- “import_text” reworded the description of “hints” cosmetic
- “import_text” reworded the description of “text” cosmetic
- “import_text” reworded the description of “token” cosmetic
- “list_my_programs” reworded the description of “token” cosmetic
- “list_public_runs” reworded the description of “limit” cosmetic
- “list_public_runs” reworded the description of “program” cosmetic
- “list_public_runs” reworded the description of “program_hash” cosmetic
- “list_runs” reworded the description of “program_id” cosmetic
- “list_runs” reworded the description of “token” cosmetic
- “load_program” reworded the description of “program_id” cosmetic
- “load_program” reworded the description of “token” cosmetic
- “load_run” reworded the description of “run_id” cosmetic
- “load_run” reworded the description of “token” cosmetic
- “login” reworded the description of “token” cosmetic
- “preview_timeline” reworded the description of “program” cosmetic
- “preview_timeline” reworded the description of “run” cosmetic
- “save_program” reworded the description of “program” cosmetic
- “save_program” reworded the description of “token” cosmetic
- “search_public_recipes” reworded the description of “environment” cosmetic
- “search_public_recipes” reworded the description of “query” cosmetic
- “validate_program” reworded the description of “program” cosmetic
- “visualize_schedule” reworded the description of “allowInvalid” cosmetic
- “visualize_schedule” reworded the description of “program” cosmetic
- “list_my_programs” made “token” optional cosmetic
- “load_program” made “token” optional cosmetic
- “save_program” made “token” optional cosmetic
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 74
First indexed and scored.
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 24 Sept 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 Aug 2026 | 10 Nov 2026 | RSA 2048 | SHA256-RSA | 6b3bf11ba01efeeeb5247055757b32beab0 |
| 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. | present | 19718 | 13 | Verified |
| rhylthyme.com. | absent | 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 https://www.redditstatic.com; 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 https://www.redditstatic.com https://alb.reddit.com https://pixel-config.reddit.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 |
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 →
analyze_schedule Analyze schedule timing ~307
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` (or `program_id`) it also predicts durations from recorded runs; see rhylthyme://guide/tools.
| Name | Type | Req | Description |
|---|---|---|---|
| finishAt | string | – | ISO 8601 datetime everything must END at, e.g. '2026-11-26T18:00:00-05:00'. Start times are worked backwards from it. |
| history | array | – | Recorded runs of this program (from load_run); adds predicted durations. |
| predictionContext | object | – | Optional: environmentId, userTags (variance factors), userId, programVersion, minIdentical, minModel, corrThreshold, verdicts. See rhylthyme://guide/tools. |
| program | object | yes | Program JSON; shape under validate_program. |
| program_id | string | – | Saved program UUID: loads the user's own recorded runs as the history. |
| startAt | string | – | ISO 8601 start datetime. Ignored with finishAt. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
| useDurations | string | – | planned (default): analyse the program as authored. predicted: as the history says it will run. |
| Name | Type | Req | Description |
|---|---|---|---|
| actorPeak | object | yes | – |
| bindingConstraints | array | – | – |
| criticalPath | array | yes | – |
| durationsUsed | string | – | – |
| inFlight | array | – | – |
| makespan | string | yes | – |
| makespanSeconds | number | yes | – |
| name | – | yes | – |
| plannedMakespan | string | – | – |
| plannedMakespanSeconds | number | – | – |
| predictedCriticalPath | array | – | – |
| predictedMakespan | string | – | – |
| predictedMakespanSeconds | number | – | – |
| programId | – | yes | – |
| resourceConflicts | array | yes | – |
| steps | array | yes | – |
| tracks | array | yes | – |
| validation | object | – | – |
| wallClock | – | yes | – |
No examples provided.
calibrate_program Propose durations from recorded runs ~218
Propose durations for a saved program from its recorded runs: median as the default, P10 to P90 as the range, never narrower than the author's, with the evidence per step and the effect on total length. Saves nothing: pass `accept` to get the calibrated program, then save_program. Needs the user's Rhylthyme account.
| Name | Type | Req | Description |
|---|---|---|---|
| accept | – | – | Step ids to accept, or "all": also returns the calibrated program. Nothing is saved either way. |
| history | array | – | Run records to use instead of the stored ones. |
| k | integer | – | Measurements a step needs for a proposal (default 5). |
| program | object | – | Program JSON to calibrate; omit to use program_id's saved JSON. |
| program_id | string | – | Saved program UUID whose recorded runs are the evidence. |
| since | string | – | Only runs started on or after this date (YYYY-MM-DD or ISO). |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
create_environment Define equipment limits ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| actors | integer | – | How many people can work at once (default 1). |
| description | string | – | – |
| name | string | yes | – |
| resourceConstraints | array | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
get_renderer_source Get timeline renderer source ~61
Return the open-source timeline renderer's JavaScript (Apache-2.0, ~9KB, no dependencies) to paste into a <script> in an HTML artifact whose sandbox blocks external scripts; then call Rhylthyme.renderTimeline(container, program).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
import_from_source Import from an external source ~202
Import a recipe or protocol from a URL or service into a program. source: spoonacular, themealdb (recipes); protocolsio, opentrons, benchling (lab); cooklang (.cook URL). action: search (no login), import (query = URL or id), random. import, random and benchling need the account. `enrich: true` splits an import into parallel tracks. Then call visualize_schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| enrich | boolean | – | With action='import': split the import into parallel tracks with cross-track triggers. One model call, capped per day. |
| query | string | – | Keywords (search), or the URL or id (import). |
| source | string | yes | – |
| text | string | – | Pasted source (an Opentrons .py) instead of a URL. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
import_text Import pasted text ~210
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. Use when the user pastes the steps and no URL importer fits. Needs the user's Rhylthyme account. Capped per day; you can instead author the program yourself and call validate_program.
| Name | Type | Req | Description |
|---|---|---|---|
| deadline | string | – | When everything must be finished, if the user said: '18:00', 'dinner at six', an ISO datetime. |
| environmentType | string | yes | kitchen, lab, events, gym or generic. |
| hints | string | – | Equipment and people limits in the user's words, e.g. 'one oven, two burners, one cook'. |
| text | string | yes | The source text, all of it, as the user wrote or pasted it. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
list_my_programs List my saved programs ~46
List the user's saved programs. Needs the user's Rhylthyme account.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
list_public_runs List contributed 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 login needed. Pass `program` or `program_hash`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Runs to return, newest first (default 50). |
| program | object | – | Program JSON to look up instead; hashed here. |
| program_hash | string | – | Program hash, 'sha256:' + 64 hex (a run record's programVersion). |
No output schema declared.
No examples provided.
list_runs List recorded 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.
| Name | Type | Req | Description |
|---|---|---|---|
| program_id | string | yes | Program UUID from list_my_programs. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
load_program Open a saved program ~70
Open one of the user's saved programs by id: summary plus live-timeline URL. Needs the user's Rhylthyme account.
| Name | Type | Req | Description |
|---|---|---|---|
| program_id | string | yes | Program UUID from list_my_programs. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
load_public_recipe Open a public program ~46
Open a public catalog entry by id: summary plus live-timeline URL (no visualize_schedule call needed).
| Name | Type | Req | Description |
|---|---|---|---|
| program_id | string | yes | Program UUID (from search_public_recipes) |
No output schema declared.
No examples provided.
load_run Open a recorded 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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | Run UUID from list_runs. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
login Connect Rhylthyme account ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | 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 Preview timeline image ~111
Return a static Gantt image of a program, for 'show me a preview' or 'a picture of the timeline'. Image and caption only; use visualize_schedule for the live URL. Planned versus actual: pass `run` (from load_run) to draw the real bars over the plan.
| Name | Type | Req | Description |
|---|---|---|---|
| program | object | yes | Program JSON; shape under validate_program. |
| run | object | – | A recorded run of the same program (the `run` object from load_run): draws planned versus actual. |
No output schema declared.
No examples provided.
review_program Review an imported 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.
| Name | Type | Req | Description |
|---|---|---|---|
| program | object | yes | Program JSON; shape under validate_program. |
| source_text | string | – | The source text (recipe, protocol), if you have it. |
| source_url | string | – | Its URL, when the text is not to hand. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
save_program Save to my account ~72
Save a program to the user's account ('save this for later'); the same programId updates it. Needs the user's Rhylthyme account.
| Name | Type | Req | Description |
|---|---|---|---|
| program | object | yes | Program JSON; shape under validate_program. |
| token | string | – | Access token from the login tool. Omit when the account is connected. |
No output schema declared.
No examples provided.
search_public_recipes Search the public catalog ~94
Search the public catalog of recipes, lab protocols, event templates and workouts by name or keyword. Returns ids, names, descriptions and URLs; no login. Pass an id to load_public_recipe.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Which catalog: kitchen (default), laboratory, event or gym. |
| limit | integer | – | – |
| query | string | – | Keyword; matches name and description. Empty returns the newest entries. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| environment | – | yes | – |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
validate_program Validate a program ~293
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 fix; apply the fixes and re-run until valid. Pure computation.
| Name | Type | Req | Description |
|---|---|---|---|
| program | object | yes | Program JSON: {programId, name, environmentType?, actors?, tracks: [{trackId, name, steps: [{stepId (unique program-wide), name, task?, duration, startTrigger, replicates?, choice?}]}], resourceConst… |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| info | array | – | – |
| stats | – | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
visualize_schedule Publish a live timeline ~117
Publish a program as a live timeline and return its URL. This is the deliverable for ANY schedule you produce ('plan this so it all finishes at 6', 'when do I start each thing'): never describe a schedule in prose. Validates first and refuses an invalid program with fix hints. Also returns an ASCII Gantt and an itinerary to quote.
| Name | Type | Req | Description |
|---|---|---|---|
| allowInvalid | boolean | – | Publish despite validation errors. Only when the user explicitly wants an imperfect draft shared. |
| program | object | yes | Program JSON; shape under validate_program. |
| Name | Type | Req | Description |
|---|---|---|---|
| imageUrl | – | yes | – |
| makespanSeconds | number | yes | – |
| shareId | – | yes | – |
| url | string | yes | – |
| warnings | array | yes | – |
No examples provided.
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 78 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 19 tools: validate_program, analyze_schedule, visualize_schedule, import_from_source, import_text, and 14 more. Their descriptions and schemas cost roughly 2,441 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.