Home / MCP registry index / com.courseprofiler/courseprofiler
CourseProfiler
com.courseprofiler/courseprofiler in the official MCP registry.
Endpoint https://courseprofiler.com/mcp.
The registry describes it as: Race course profiling, catalog search, course submission, and personalized race plans.
We read its 26 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
create_race_plan search_race_catalog import_course enrich_course_waypoints generate_course_segments generate_runner_profile submit_course get_course_submission_requirements get_race_plan_requirements get_runner_profile_requirements get_artifact_upload_requirements get_job get_artifact validate_course_profile validate_runner_profile export_race_plan_pdf build_runner_profile_from_strava analyze_activity inspect_analysis compare_execution inspect_runner_profile assess_finish_time_goal compare_pacing_strategies import_profile_attachment get_storage_readiness get_activity_submission
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-courseprofiler-courseprofiler)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.