Is com.courseprofiler/courseprofiler up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-06-18.
A stock client connected with no credential and negotiated 2025-06-18. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-06-18 |
| Server says it is | courseprofiler 0.1.0 |
| Answered in | 768 ms |
| Endpoint checked | https://courseprofiler.com/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (HTTP 403)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://courseprofiler.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (HTTP 403)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (HTTP 403)./.well-known/http-message-signatures-directory |
Read at https://courseprofiler.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 24 tools: analyze_activity, assess_finish_time_goal, build_runner_profile_from_strava, compare_execution, compare_pacing_strategies, create_race_plan, enrich_course_waypoints, export_race_plan_pdf, generate_course_segments, generate_runner_profile, get_artifact, get_artifact_upload_requirements, get_course_submission_requirements, get_job, get_race_plan_requirements, get_runner_profile_requirements, import_course, import_profile_attachment, inspect_analysis, inspect_runner_profile, search_race_catalog, submit_course, validate_course_profile, validate_runner_profile.
Its tools changed between 2026-09 and 2026-10:
analyze_activity: output schema changedbuild_runner_profile_from_strava: output schema changedcompare_execution: output schema changedcreate_race_plan: output schema changedenrich_course_waypoints: output schema changedexport_race_plan_pdf: output schema changedgenerate_course_segments: output schema changedgenerate_runner_profile: output schema changedget_artifact: description, output schema changedget_job: output schema changedimport_course: output schema changedsubmit_course: input schema, output schema changedvalidate_course_profile: output schema changedvalidate_runner_profile: output schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.courseprofiler/courseprofiler |
|---|---|
| Title | CourseProfiler |
| Description | Race course profiling, catalog search, course submission, and personalized race plans. |
| Endpoint | https://courseprofiler.com/mcp |
| Publisher repository | none listed |
| Version | 0.1.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt