Servidor MCP de Muffed
Qué servidores del registro oficial de MCP son de Muffed, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.
leído el 2026-10-13
- Nombre en el registroai.muffed/muffedverificado en el registro MCP
El nombre en el registro está bajo muffed.ai. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.
- Estadorespondecomprobado el 2026-10-13
- Herramientas15
- El servidor se llamamuffed
- Versión del servidor1.0.0
- Versión del protocolo2025-06-18
El 2026-10-13 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 652 ms.
get_current_insightsMuffed's published editorial reads on what is real in the NFL right now — each one a dated, sourced claim with its supporting figures, from the /trends board.
query_stat_leadersTop entities on one verified metric for one season, pre-sorted, each with the source's own rank and the population it was ranked against. Takes a verified panel metric key.
get_entity_metricsThe verified figures Muffed holds for one NFL player or one NFL team (by name or abbreviation, e.g. "Bijan Robinson" or "DEN"), with the source's rank where one exists. By default the headline figures for that player or team; scope "all"…
compare_entitiesTwo players or two teams shown side by side — by default on the metrics that matter for their position, on named metrics when `metrics` is set, and on the full set with all:true. Each side carries its source rank. States both figures and…
get_metric_definitionMuffed's published definition of a verified metric — what it measures, in plain language, from the glossary page for that term — plus which seasons it actually covers, how it is ranked, its licence and its attribution. Accepts a metric…
list_metricsWhat Muffed can answer on. By default a summary of metric families with their counts and season coverage; with search or detail:true, individual metric keys. Returns keys and coverage only, never figures.
search_metricsThe verified metrics that match a topic — e.g. 'screens', 'blitz', 'time to throw' — ranked by a text match over each metric's key, label, common names and board description. Up to 20 entries, each with its key, subject, season coverage…
verify_claimChecks structured claims against Muffed's verified panel. Each claim comes back confirmed, wrong (with the actual value), or unverifiable (with the metric's real season coverage). Takes structured fields only, not sentences.
get_backfieldMuffed's published handcuff page for one team's backfield, plus the current depth chart and injury status from Sleeper. Answers who backs up a starter, and who replaces one who is out.
run_stat_queryComputes an NFL figure from a structured query rather than looking one up: a population (position, qualifying threshold), a window (seasons, weeks, a team span, a coach's tenure), one named measure, and one operation (leaders, rank…
sleeper_find_leaguesLists the NFL leagues a Sleeper username belongs to, with each league's id. Muffed stores nothing about the requester.
sleeper_get_leagueOne league's name, season, size, current week, detected scoring format, and the manager-to-roster map.
sleeper_matchup_previewBoth sides of a league matchup, with the verified figures Muffed holds for the players involved and each team's record. Muffed does not project outcomes, name a winner, or recommend a lineup.
sleeper_roster_storiesOne team's roster mapped to the verified figures and published Muffed surfaces for each player. Players Muffed does not cover are listed as uncovered rather than omitted.
sleeper_standings_storyLeague standings derived from Sleeper's roster settings — records, points for, and points against where available. Sleeper publishes no standings endpoint, so these are computed from the roster rows.
Cómo conectar
Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:
{
"mcpServers": {
"muffed": {
"type": "http",
"url": "https://muffed.ai/api/mcp"
}
}
}Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.