Home / MCP registry index / io.github.mcp-dir/mfit-mcp

MFIT Personal

io.github.mcp-dir/mfit-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_mfit. Source: github.com/mcp-dir/mfit-mcp.

The registry describes it as: Client, workout, body composition, retention and finance management for personal trainers.

We read its 48 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http mfit-mcp https://api.mcp.ai/p_mfit

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mfit-mcp": {
      "url": "https://api.mcp.ai/p_mfit"
    }
  }
}

VS Code

code --add-mcp '{"name":"mfit-mcp","type":"http","url":"https://api.mcp.ai/p_mfit"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

mfit_list_accounts mfit_get_profile mfit_client_list mfit_client_get mfit_client_list_groups mfit_client_write_create mfit_client_write_update mfit_client_write_deactivate mfit_get_client_count mfit_get_client_notes mfit_get_client_notes_write mfit_client_files_list mfit_client_files_get mfit_client_files_write mfit_client_files_delete mfit_get_client_workouts mfit_workout_get_routine mfit_workout_get_session mfit_workout_write_create_routine mfit_workout_write_update_routine mfit_workout_write_archive_routine mfit_workout_write_unarchive_routine mfit_workout_write_create_session mfit_workout_write_add_exercise mfit_workout_write_update_serie mfit_workout_delete_routine mfit_workout_delete_session mfit_workout_delete_exercise mfit_get_workout_library mfit_search_exercises mfit_get_exercise_favorites mfit_get_user_exercises mfit_get_client_evaluations mfit_get_training_frequency mfit_get_retention mfit_get_finances mfit_get_invoices mfit_get_anamnesis_models mfit_get_today_checkins mfit_get_training_ranking mfit_get_feedbacks mfit_get_retention_clients show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-mfit-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-mfit-mcp)

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.

Finance and markets MCP servers