Ir para o conteúdo
Logo de Hyperhuman

Servidor MCP de Hyperhuman

Quais servidores MCP são de Hyperhuman, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-11-01

← Voltar para Hyperhuman

De quem é o servidor
  • Nome no registrocc.hyperhuman/hyperhumanverificado no registro MCP

O nome no registro fica sob hyperhuman.cc. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-11-01
  • Estadorespondeverificado em 2026-11-01
  • Ferramentas45
  • O servidor se chamahyperhuman
  • Versão do servidor0.1.0
  • Versão do protocolo2025-06-18

Em 2026-11-01 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 205 ms.

Um agente deve conectá-loAinda não está claro
  • Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
  • Verificado em 3 dos 7 dias necessários para julgar a confiabilidade.

Depois de conectar

  • Mantenha a aprovação para create_drop, export_drop: elas apagam, enviam ou pagam sem avisar.
  • create_drop, create_workout, update_workout, create_program, update_program alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.
  • Parâmetros sem tipo ou descrição em 42 de 45 ferramentas: confira os argumentos antes de chamar.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

Medido todo diaverificações diárias: 3, a primeira em 2026-11-01
  • Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 3 até agora
  • Respondeumedindo3 das 7 verificações diárias necessárias para mostrar a porcentagem
  • Mediana da primeira resposta167 ms
  • Espaço no contexto do agente≈ 7.049 tokensas definições de todas as ferramentas (45), que o agente carrega a cada turno
  • Definições das ferramentasB · 84 de 100
  • Resultados tipados45 de 45 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
  • Parâmetros sem descrição: em 42 de 45

O que um agente consegue fazer com ele

  • consegue · generate workout programs for app members
  • incerto · build exercise video libraries from stock or own footage
  • incerto · deliver adaptive workout journeys inside a gym or fitness app

Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?

Vale conferir

  • Ferramentas que apagam, enviam ou pagam, marcadas como não destrutivas: create_drop, export_drop
  • Ferramentas que alteram dados, em um servidor que responde sem login: create_drop, create_workout, update_workout, create_program, update_program

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

Ferramentas que oferece45 ferramentas · lido em 2026-11-01
  • get_integration_plan

    Returns an integration strategy and step-by-step plan for Hyperhuman workouts or programs: embed (iframe), stream videos (VOD export), or custom player (API + playlist). Use when the user asks how to integrate Hyperhuman or what…

  • list_sample_workouts

    Returns a workout carousel for sample-workout prompts. When the user is connected via OAuth, lists up to 8 team workouts through the Internal API (Bearer token only — no Content API key required). When not connected, returns up to 6…

  • get_workout_details

    Returns workout metadata, preview assets, and summary. Use when the user selects a workout or asks for details about a specific workout. sample-* ids return a curated sample detail (no auth). Connected team workout ids use the Internal…

  • get_workout_playlist

    Returns playlist segments with timing and media pointers (progressive MP4/M4A URLs, typically ~7 days). sample-* ids return a curated sample playlist (no auth, no live media URLs). Connected org ids use the Content API when the team has…

  • get_embed_code_samples

    Returns static copy-paste code templates for workout embeds (keyHandshake iframe), program page embeds, custom player JavaScript, or Content API cURL snippets. All samples contain only placeholder values (YOUR_ORG_ID, YOUR_API_KEY) — no…

  • list_team_workouts

    Returns workouts for the authenticated user's team via Internal API. Use when the user asks to see my team's workouts, my team workouts, or their organization workout library. Requires OAuth. Not for curated sample workouts or guest embed…

  • get_team_workout

    Returns full details of a workout from the team. Use when the user selects a workout or asks for details about a specific workout.

  • list_team_programs

    Returns workout programs (collections) for the authenticated user's team. Use when the user asks to see programs, training plans, or workout collections.

  • get_team_program

    Returns full details of a workout program from the team. Use when the user selects a program or asks for program structure.

  • list_team_goals

    Returns fitness goals available for programs. Use when creating or generating programs to get valid goal IDs.

  • list_workout_categories

    Returns workout categories for workouts. Use when creating or updating workouts to get valid category_ids.

  • list_muscle_groups

    Returns muscle groups for exercises. Use when updating exercise metadata or filtering exercises.

  • list_equipment

    Returns equipment for exercises. Use when updating exercise metadata or filtering exercises.

  • get_team_usage

    Returns usage quotas for the authenticated team (e.g. social drop export count and limits). Use when the user asks about usage, quotas, or limits.

  • get_session_summary

    Returns team name, plan label, and usage limits for the connected account. Use only when the user explicitly asks about their team, plan, or usage quotas.

  • get_api_usage_stats

    Returns API key usage statistics for the current user's team. Use when the user asks about API usage, request counts, or rate limits.

  • list_team_drops

    Returns social drops (videos, covers, copy) for the team. Use when the user asks about drops, social assets, or ready-to-download content.

  • get_dashboard_summary

    Returns dashboard summary: latest created workouts with stats and ready-to-download items. Use when the user asks about dashboard, recent workouts, or content ready for download.

  • create_drop

    Creates a social drop from an exercise, exercise group, workout, or program. Use when the user wants to create social media content from existing content.

  • regenerate_drop_copy

    Regenerates AI copy pack (hook, caption, hashtags, CTA) for a drop. Use when the user wants to refresh or improve the social copy.

  • regenerate_drop_cover

    Regenerates AI cover image for a drop. Use when the user wants a new cover for the social asset.

  • export_drop

    Exports drop assets for a channel (video URL, cover URL, copy pack). Use when the user wants to download assets or prepare a drop for external publishing.

  • generate_program

    Generates an AI training program using team workouts. Use when the user wants to create a multi-week program from their workout library.

  • create_workout

    Creates a workout from exercise and rest instances. Use when the user wants to build a custom workout. Provide either exercise_map (ordered array of instance IDs from create_exercise_instance and create_rest_instance) or instances (raw…

  • update_workout

    Updates an existing workout. Use when the user wants to change workout name, description, difficulty, visibility, or exercise structure. When only partial fields are provided (e.g. name), the current workout data is fetched and merged…

  • create_program

    Creates a workout program from team workouts. Use when the user wants to organize workouts into a multi-week program. Requires goal_ids (1-2) and workout_ids (min 2).

  • update_program

    Updates an existing program. Use when the user wants to set duration, workouts per week, or edit program metadata. When updating, provide full program data (goal_ids, workout_ids, visibility, difficulty) from get_team_program and merge…

  • update_exercise_group

    Updates an exercise group. Use when the user wants to change name, exercises, rounds, or rest time.

  • update_exercise_metadata

    Updates exercise metadata (name, muscle groups, categories, equipment, skill level). Use when the user wants to fix or improve exercise tagging. Only team-owned exercises can be updated; stock exercises are read-only. Provide at least one…

  • list_stock_programs

    Returns platform stock programs (publisher programs). Use when the user wants to browse or clone stock programs.

  • clone_stock_programs

    Clones stock programs to the user's team. Use when the user wants to add publisher programs to their library.

  • update_drop

    Updates a drop title or channel preset. Use when the user wants to change drop display title or default export channel. For copy changes use regenerate_drop_copy.

  • list_team_exercises

    Returns exercises from the team library. Use when the user wants to browse exercises, find exercises for workouts, or manage the library.

  • get_team_exercise

    Returns full details of an exercise from the team library. Use when the user selects an exercise or asks for exercise details.

  • create_exercise_instance

    Creates an exercise instance with duration/reps, pace, weight, RPE. Use when building a workout manually - create instances for each exercise, then pass instance IDs to create_workout. Stock and team exercises can be used directly via…

  • create_rest_instance

    Creates a rest/break instance for use between exercises in a workout. Use when building a workout manually - create rest instances, then include their IDs in create_workout exercise_map. Workout cannot start or end with rest.

  • create_exercise_group

    Creates an exercise group (circuit or sets). Use when the user wants to group exercises for circuits or micro-workouts. Requires at least 2 exercise IDs.

  • generate_video_clip

    Generates an AI exercise video from a trainer photo (CloneMotion). Use when the user wants to create exercise videos without filming. Before calling, ensure you have the target exercise and image source (upload URL or saved trainer image…

  • get_video_generation_status

    Returns status and result of a CloneMotion video generation job. Use when the user wants to check if a generated video is ready or view the generated variants. Generation can take a few minutes; if status is pending or running, ask the…

  • generate_workout

    Generates an AI workout via Content API. Use when the user wants to create a personalized workout on-the-fly. Returns workout structure (not persisted to team library by default).

  • recommend_workouts

    Returns ranked workout recommendations from the organization library (up to 12 workouts in the tool response; optional limit up to 20 is sent to the API). Use when the user wants instant suggestions based on profile (faster than generate).

  • adapt_workout

    Adapts an existing workout for a user profile. Use when the user wants to customize a workout (duration, difficulty, equipment) without generating from scratch.

  • recommend_plans

    Returns ranked program recommendations from the organization library (up to 12 programs in the tool response; optional limit up to 20 is sent to the API). Use when the user wants instant program suggestions.

  • adapt_plan

    Adapts an existing program for a user profile. Use when the user wants to customize a program.

  • health_check

    Returns MCP server readiness status with a fixed ready message. Use when the user asks if the Hyperhuman app is working, reachable, or connected.

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

{
  "mcpServers": {
    "hyperhuman": {
      "type": "http",
      "url": "https://mcp.hyperhuman.cc/mcp"
    }
  }
}

Adicionar

Claude Code, no terminal

claude mcp add --transport http hyperhuman https://mcp.hyperhuman.cc/mcp

Adicionar ao CursorAdicionar ao VS Code

claude.ai, ChatGPT e outros clientes: adicione https://mcp.hyperhuman.cc/mcp como conector personalizado nas configurações.

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.