rhylthyme-mcpCAUTION
MCP server for human-executed, resource-constrained schedules: validate, analyze, import and publish live timelines on rhylthyme.com. Source of mcp.rhylthyme.com.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://claude.ai/directory/rhylthyme) [](https://mcpservers.org/servers/rhylthyme/rhylthyme-mcp)
A Model Context Protocol server for schedules that a person executes: cooking several dishes so they finish together, running a bench protocol with overlapping incubations, calling an event, running a workout. An agent describes the process, the server validates and analyzes the resulting program, and publishes it as a live timeline on rhylthyme.com that the person follows on their phone.
This repository is the source of the server that runs at mcp.rhylthyme.com. It is the same code as mcp-api/ in the rhylthyme-server application, copied here with the static assets it needs so it can be read, tested and self-hosted.
Try it: ask for a workout
Connect the server (in claude.ai, Claude Desktop or mobile, add Rhylthyme from the Claude Connectors Directory; in Claude Code, /plugin marketplace add rhylthyme/rhylthyme-mcp then /plugin install rhylthyme@rhylthyme; anywhere else, add https://mcp.rhylthyme.com/gym/mcp as a connector), then say what you want in plain words:
Two of us in a garage gym: one kettlebell, one pull-up bar, one jump rope. Thirty minutes, two rounds, and nobody stands around waiting for equipment. Make it a Rhylthyme timeline.
You write no JSON. The assistant does, and the server keeps it honest. With that prompt Claude made three tool calls:
3c80223ad092OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add rhylthyme-mcp --env RHYLTHYME_TOKEN=${RHYLTHYME_TOKEN} --env SUPABASE_ANON_KEY=${SUPABASE_ANON_KEY} -- npx -y [email protected]{
"mcpServers": {
"rhylthyme-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"RHYLTHYME_TOKEN": "${RHYLTHYME_TOKEN}",
"SUPABASE_ANON_KEY": "${SUPABASE_ANON_KEY}"
}
}
}
}Exposed tools (19)
12 read · 7 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
analyze_schedule | write | |
calibrate_program | read | |
create_environment | write | |
get_renderer_source | read | |
import_from_source | write | |
import_text | write | |
list_my_programs | read | |
list_public_runs | read | |
list_runs | read | |
load_program | read | |
load_public_recipe | read | |
load_run | write | |
login | read | |
preview_timeline | read | |
review_program | read | |
save_program | write | |
search_public_recipes | read | |
validate_program | read | |
visualize_schedule | write |
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (5 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (8)
__init__.cpython-312.pyc
server.cpython-312.pyc
test_bridge.cpython-312-pytest-9.0.2.pyc
assert.equal(meta("/.well-known/oauth-protected-resource/../../etc").resource, "https://mcp.rhylthyme.com/mcp", "junk paths fall back");server.main(["--url", "http://127.0.0.1:9/mcp"])
assert.ok(!/[--]/.test(d), `${vertical}/${t.name} has hidden characters`);@modelcontextprotocol/server, mcp-handler, zod, @modelcontextprotocol/client, @resvg/resvg-js
mcp-api/labmcp-check-cases.json
Gates applied: no_behavioural_pass.
3c80223ad092full audit observations/trust-audit/mcp-server/rhylthyme__rhylthyme-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 3c80223ad092 | CAUTION | B | 89 | first audit |
Questions
What is the rhylthyme-mcp MCP server?
MCP server for human-executed, resource-constrained schedules: validate, analyze, import and publish live timelines on rhylthyme.com. Source of mcp.rhylthyme.com.
What tools does rhylthyme-mcp expose?
19 in total: 12 read-only, 7 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is rhylthyme-mcp safe to connect to an agent?
With care. The audit graded it B (89/100) and found 8 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does rhylthyme-mcp need?
It reads RHYLTHYME_TOKEN and SUPABASE_ANON_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does rhylthyme-mcp run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as rhylthyme-mcp at 1.3.0.
How current is this page?
The grade is for one exact copy of the source (3c80223ad092), read on 2026-10-12. The repository is watched and re-audited when it changes.