Futurefin Mcp Parity

Load this skill whenever a change touches the surface of FutureFin's API or its embedded MCP server: adding/removing/renaming a route or handler, changing a request/response field, adding an MCP tool, or auditing whether the MCP catalog is up to date. It owns the parity discipline (every HTTP-surface change must end in exactly one of: tool added/updated, deliberate omission recorded, or n/a), the decision rubric for WHEN a tool is pertinent vs excluded, the standing register of deliberate omissions and pending gaps, and the step-by-step recipe to add or update a tool. Triggers: "add an MCP tool", "añadir una tool", "does this endpoint need a tool?", "the MCP is out of date", "el MCP se ha quedado atrás", "tools/list", "frozen catalog", "tools_list_returns_exactly_the_v1_catalog", "update the tool catalog", "new handler — MCP?", "extract a *_core", "preview/confirm", "tool annotations", "68 tools". Do NOT use it for WHY tools share core fns / live-role auth (futurefin-architecture-contract D14/D15), the catalog's per-tool semantics (.claude/api-routes.md §MCP), MCP env vars and the write toggle (futurefin-config-and-flags), how to run the MCP test suites (futurefin-validation-and-qa / .claude/tests.md), or generic merge gates (futurefin-change-control — it routes here, this skill is the evaluation it routes to).

mkdir -p ~/.claude/skills/futurefin-mcp-parity
curl -L https://claudskills.com/skills/futurefin-mcp-parity/SKILL.md \
  -o ~/.claude/skills/futurefin-mcp-parity/SKILL.md

@misc{futurefin-mcp-parity-2026,
  author    = {maxlainz},
  title     = {Futurefin Mcp Parity [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/futurefin-mcp-parity/}
}