intervals-icu-sync (rbrands/intervals-icu-sync) is an MCP server listed on the M8ven Trust Index. It scores 60 out of 100, grade C. It declares 16 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
60/100

intervals-icu-sync

Connect any GenAI tool to your intervals.icu data — includes MCP server, Python scripts, system prompts and coaching logic based on Joe Friel.

→ rbrands/intervals-icu-sync· listed on github_repo_search

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

rbrands

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — check_plan_tss (line 1869: result = subprocess.run()
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: INTERVALS_API_KEY, OAUTH_TOKEN_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes11 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

prepare_week_data

Fetch all training data, run fueling/week analysis, and consolidate output.

get_coach_input

Return the consolidated weekly coach input as JSON.

get_fueling_analysis

Return the carbohydrate fueling analysis for the specified week as JSON.

get_latest_metrics

Return the most recent athlete performance metrics as JSON.

get_activity_streams_sampled

Return sampled activity streams for a single activity as JSON.

list_library_workouts

List own library workouts for the configured athlete (ATHLETE_ID).

save_week_plan

Save a weekly training plan as JSON to data/plans/week_plan.json.

validate_week_plan

Validate a training plan JSON against the upload schema.

upload_week_plan

Upload the saved weekly training plan to intervals.icu.

get_latest_activities

Return a compact, latest-first list of activities for the current week.

check_plan_tss

Check whether a generated week plan matches a deterministic TSS reference.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configFASTMCP_ALLOWED_HOSTyour-tunnel-hostname.example.com
configFASTMCP_HOST
configFASTMCP_PORT
configMCP_TRANSPORT
configWEBSITE_INSTANCE_ID
configMCP_RPC_EVENT_LOG_LEVEL
configMCP_TRACE_RESPONSE_JSON
configMCP_TRACE_RESPONSE_PREVIEW_LIMIT
configWEBSITE_SLOT_NAME
configWEBSITE_HOSTNAME
configMCP_STATELESS_HTTP
configINTERVALS_DEV_MODE
configATHLETE_IDyour athlete ID, also under Settings → Developer Settings
🔐 secretINTERVALS_API_KEYfound in intervals.icu under Settings → Developer Settings
configSCRIPT_TIMEOUT_SECONDS
configPREPARE_WEEK_TIMEOUT_SECONDS
configAGENT_NAME
configDISCIPLINE
configRESPONSE_LANGUAGE
configVECTOR_STORE_NAME
configSKILL_NAME
configTOOLBOX_NAME
configMODEL
configMESSAGE
configINTERVALS_RAW_DIR
configINTERVALS_PROCESSED_DIR
configLOOKBACK_DAYS
configOAUTH_CLIENT_STORAGE_ACCOUNT
configOAUTH_CLIENT_TABLE_NAME
🔐 secretOAUTH_TOKEN_SECRET
configINTERVALS_PROMPTS_LIBRARY_DIR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployAPPLICATIONINSIGHTS_CONNECTION_STRING
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

16/16 tools missing one or more hints — prepare_week_data (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_coach_input (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_fueling_analysis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

4 tools perform destructive updates without destructiveHint — validate_week_plan deletes at line 833 (temp_plan_path.unlink(missing_ok=True)); validate_week_plan deletes at line 1681 (tmp_path.unlink(missing_ok=True)); upload_week_plan deletes at line 1813 (tmp_path.unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — check_plan_tss (line 1869: result = subprocess.run()

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool test coverage

Only 4/16 tools referenced in tests (25%)

Write tests that reference each tool by name so every tool has at least one test.

Tool description accuracy

check_plan_tss: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/rbrands/intervals-icu-sync?variant=verified)](https://m8ven.ai/mcp/rbrands/intervals-icu-sync)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: a6ba0f9a923f718e3b16b18bd77902f0e147049f
code hash: 80203ec41226868f15311e8b1e7eeb4cb3e9cffbcb35c94f177f8a341ee2573c
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client