MCP servers observed by Lowdown
io.github.mcp-dir/mfit-mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 50 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.mcp-dir/mfit-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.mcp-dir/mfit-mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-19: server version changed
- 2026-11-16: server version changed
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 48 → 50
What tools does it list?
50 tools on 2026-11-19:
authenticateconnectmarketplacemfit_client_files_deletemfit_client_files_getmfit_client_files_listmfit_client_files_writemfit_client_getmfit_client_listmfit_client_list_groupsmfit_client_write_createmfit_client_write_deactivatemfit_client_write_updatemfit_get_anamnesis_modelsmfit_get_client_countmfit_get_client_evaluationsmfit_get_client_notesmfit_get_client_notes_writemfit_get_client_workoutsmfit_get_exercise_favoritesmfit_get_feedbacksmfit_get_financesmfit_get_invoicesmfit_get_physical_assessmentmfit_get_profilemfit_get_retentionmfit_get_retention_clientsmfit_get_today_checkinsmfit_get_training_frequencymfit_get_training_rankingmfit_get_user_exercisesmfit_get_workout_librarymfit_list_accountsmfit_list_physical_assessmentsmfit_search_exercisesmfit_workout_delete_exercisemfit_workout_delete_routinemfit_workout_delete_sessionmfit_workout_get_routinemfit_workout_get_sessionmfit_workout_write_add_exercisemfit_workout_write_archive_routinemfit_workout_write_create_routinemfit_workout_write_create_sessionmfit_workout_write_unarchive_routinemfit_workout_write_update_routinemfit_workout_write_update_seriereport_bugshow_versiontoolkit_info
MCP Registry declaration
- Registry name:
io.github.mcp-dir/mfit-mcp - Declared version: 0.1.0
- Status: active
- Declared hosts:
api.mcp.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.mcp-dir/mfit-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.mcp-dir/mfit-mcp?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).