Home / MCP registry index / me.phor/phorme-training

Phorme Training

me.phor/phorme-training in the official MCP registry. Endpoint https://phor.me/api/mcp. Source: github.com/nicksgoat/phorme-mcp.

The registry describes it as: Coach-built training: coaching brains, programs, race plans, gyms, clinics, demos and your log.

We read its 49 tools on 2026-10-30. 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 phorme-training https://phor.me/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "phorme-training": {
      "url": "https://phor.me/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"phorme-training","type":"http","url":"https://phor.me/api/mcp"}'

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

preview_workout_import save_workout_to_phorme preview_program_import save_program_to_phorme get_saved_training render_training_import preview_sport_week find_races plan_for_race find_coaching_brain find_gym_class book_gym_class cancel_gym_booking find_clinic find_personal_coach check_place_in_ai find_exercise_swap get_training_history get_lift_progress get_planned_sessions get_my_coaching_business start_my_coaching_brain save_program_to_my_coaching_brain send_note_to_my_members set_my_brain_rules get_my_brain_code copy_coach_from_code get_gym_report create_or_claim_place update_place set_class_schedule publish_place unpublish_place start_gym_brain set_member_cover list_held_requests answer_held_request claim_place verify_place_claim cover_member update_gym_brain publish_gym_brain set_booking_notices get_gym_billing_link get_payouts get_payout_setup_link set_owner_email search_phorme_programs get_phorme_program

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 8b22b4d7f08b1743. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

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/me-phor-phorme-training/badge.svg)](https://lazaretto.dev/mcp-registry/me-phor-phorme-training)

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.