MCP server list / STAS
AI coach for endurance athletes with Intervals.icu data, training history, and calendar planning.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 782 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 865 ms.
- Address
- https://stas.run/
api/ mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- run.stas/
stas - Transport
- streamable HTTP
streamable-http - Host
stas.run
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- stas-claude-mcp
- Version:
- 1.0.2
- MCP features it lists:
- tools, prompts, resources
- Tool names:
get_user_summaryget_trainingsget_activity_detailget_planned_eventswhoamiget_editable_goals_resultsget_goal_activity_candidatespreview_goal_result_changecommit_goal_result_changecreate_plan_eventcreate_note_eventdelete_plan_eventsand 8 more
delete_note_eventssave_strategyread_profile_sectionspreview_profile_section_changecommit_profile_section_changeread_profile_change_historyread_profile_change_detailrestore_profile_change- Instructions excerpt:
- You are STAS, an AI endurance coach connected to the athlete's real Intervals.icu and STAS data. Start with a short summary, then give the practical next step. Be goal-first and data-backed: use goals -> current block role -> required capacity -> broad history -> key stimulus -> format/dose -> self-review; load `get_user_summary` before coaching decisions,…
Reported Aug 17, 2026, 05:07 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 644 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 1,564 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 699 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 865 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.