Connect MONS Athletics and your agent gets 14 tools, among them about_mons, add_challenge, ask_coach. It answers at https://monsathletics.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 6 October 2026; the last check, on 22 November 2026, succeeded.
Find your next endurance challenge and train for it with your MONS coach.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
about_mons | What MONS Athletics is, its training method, who it is for, what it needs (iPhone and Apple Watch), and links to get started. |
add_challenge | Puts a challenge on a date after today. challenge_id is a challenge id, as find_next_challenge and ladder give them. Inputs: challenge_id, date |
ask_coach | Sends a message to their MONS coach, in the same thread as the app, and returns the coach's reply. Use for any training question: soreness, a missed session, how a session should feel. The coach may adjust their workouts. Inputs: message, today |
check_readiness | Picks the challenge to aim for from the person's training, whether they are ready for it, and what is still needed if not. Returns the next question while one is unanswered, then the challenge and verdict. Send every answer so far each time Inputs: sport, furthest_km, challenge_id, answers, today |
edit_schedule | Sets what a coming day is for (days), or what a weekday is for every week (weekly). focus none on a day hands it back to the coach for that date only; focus null clears it. Only one weekday can be the long run. Inputs: days, weekly, today |
find_next_challenge | Takes the furthest a person has run, ridden or swum and gives the first question about their training, plus every challenge in that sport. check_readiness picks the challenge once the questions are answered. Inputs: sport, furthest_km, challenge_id |
ladder | The challenge ladder in order (collected, next, ready, readiness) and the challenges on the calendar, each with the id remove_challenge takes. Inputs: today |
morning_check_in | Each day is planned on its own each morning. When the athlete's day is different, this tells the coach how many minutes they have today and what they cannot do, and the coach plans today's sessions again around it. Returns them. Takes up to Inputs: minutes, cannot_do, today |
my_profile | Whether the account is set up and subscribed, the endurance mix, kettlebells, date of birth and max heart rate. |
remove_challenge | Removes a challenge that has not happened yet, by its id from ladder on_the_calendar. Inputs: id |
schedule | The coming days: what each day is set to (rest, long run, a sport), the weekly rules, and the sessions so far. Inputs: today |
sign_up | Sets up the signed-in person's MONS account, as the app's onboarding would. Pass the challenge and answers from check_readiness when there are some. Does nothing to an account already set up. Inputs: mix, kettlebells, date_of_birth, challenge_id, answers, today |
today | Today's sessions as the coach designed them, or that today is not designed yet. Inputs: today |
update_profile | Changes how they build endurance (mix) or which kettlebells they have. Send only what changes. Inputs: mix, kettlebells |
Every block below points at https://monsathletics.com/mcp. Pick your client and copy.
claude mcp add --transport http mons-athletics https://monsathletics.com/mcp
{
"mcpServers": {
"mons-athletics": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://monsathletics.com/mcp"]
}
}
}{
"mcpServers": {
"mons-athletics": {
"url": "https://monsathletics.com/mcp"
}
}
}{
"servers": {
"mons-athletics": {
"type": "http",
"url": "https://monsathletics.com/mcp"
}
}
}{
"context_servers": {
"mons-athletics": {
"url": "https://monsathletics.com/mcp"
}
}
}{
"mcpServers": {
"mons-athletics": {
"serverUrl": "https://monsathletics.com/mcp"
}
}
}{
"mcpServers": {
"mons-athletics": {
"url": "https://monsathletics.com/mcp"
}
}
}name: MONS Athletics
version: 0.0.1
schema: v1
mcpServers:
- name: MONS Athletics
type: streamable-http
url: https://monsathletics.com/mcp{
"mcpServers": {
"mons-athletics": {
"httpUrl": "https://monsathletics.com/mcp"
}
}
}{
"mcpServers": {
"mons-athletics": {
"type": "http",
"url": "https://monsathletics.com/mcp"
}
}
}{
"mcpServers": {
"mons-athletics": {
"url": "https://monsathletics.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmonsathletics.com%2Fmcp&type=streamable_http&id=mons-athletics&name=MONS%20Athletics
It answered our last check on 22 November 2026 in 278 ms. Over 4 checks since 6 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by monsathletics.com and served from monsathletics.com, the vendor's own domain: https://monsathletics.com/mcp.
14, as returned by the server's own tools/list on 22 November 2026: about_mons, add_challenge, ask_coach, check_readiness, edit_schedule, find_next_challenge, ladder, morning_check_in, and 6 more.
It answered our last check on 22 November 2026 in 278 ms. Over 4 checks since 6 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://monsathletics.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.monsathletics. Endpoint host: monsathletics.com. ARD identifier: urn:air:com.monsathletics:mcp:mons.
First indexed 5 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.