skills.rest
maxlainz
maxlainzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

futurefin-mcp-parity

Enforces parity between FutureFin's HTTP API surface and its embedded MCP tool catalog.

1|Updated May 2, 2026
Search Tags:#MCP#API parity#tool catalog#rust backend#endpoint audit#decision rubric#futurefin
One-click install
npx skills add https://github.com/maxlainz/FutureFin --skill futurefin-mcp-parity-maxlainz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: futurefin-mcp-parity
Source: https://github.com/maxlainz/FutureFin/tree/main/.claude/skills/futurefin-mcp-parity
Command: npx skills add https://github.com/maxlainz/FutureFin --skill futurefin-mcp-parity-maxlainz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Derived API surfaces rot silently: when FutureFin's HTTP API gains a route, field, or semantic change, its embedded MCP server can drift out of sync without anything failing. This Skill forces an explicit parity decision at merge time so every HTTP-surface change ends in a tool added/updated, a deliberate omission recorded, or a documented n/a. ## Core Features & Use Cases - Parity contract enforcement: Defines the mandatory three-outcome rule for any HTTP API surface change, covering both HTTP→MCP and MCP→docs/tests directions. - Decision rubric: Provides exclusion categories (credentials, membership, OAuth, backups, infra probes) and pertinence signals (CRUD symmetry, engine inputs, conversational differential) to decide whether an endpoint warrants an MCP tool. - Standing decision register: Maintains the single home of "why is there no tool for X", including deliberate omissions, closed-gap archives, and tools-without-endpoint precedents. - Use Case: A developer adds a new endpoint to the FutureFin API and asks whether it needs an MCP tool; this Skill walks them through the rubric, records the outcome, and lists the recipe steps (core extraction, frozen catalog test, annotations, docs) to ship it in the same PR. ## Quick Start Ask the AI to evaluate whether a new or changed FutureFin API endpoint needs an MCP tool and to record the parity decision before merge.

Frequently Asked Questions about futurefin-mcp-parity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide whether a new API endpoint needs an MCP tool?▼

Run the decision rubric: check exclusion categories first (credentials, OAuth, membership, backups, infra probes), then pertinence signals like CRUD symmetry and engine inputs. Record the outcome as a tool added, a deliberate omission in the register, or n/a before merge.

How do I add a new MCP tool to an existing HTTP handler?▼

Follow the recipe: extract or reuse the handler's shared *_core function (mandatory per D14, never write tool-specific SQL), add the thin Bearer-authenticated wrapper, update the frozen catalog test, tool annotations, mcp-catalog.md, and module-map counters in the same PR.

Which API endpoints should never become MCP tools?▼

Never build tools for credential minting/revocation, OAuth protocol and consent flows, session lifecycle and password rotation, membership management, encrypted backup transport, and infra probes. These are recorded as deliberate omissions with rationale in the standing decision register.

Can an MCP tool exist without a corresponding HTTP endpoint?▼

Yes, but it must match an accepted pattern: the MCP consumer lacks context the SPA has. Four precedents exist (simulate_projection, update_fire_settings, get_settings, update_installation_settings); a fifth must name which form it follows or bring a new argument.

Why must MCP tools call shared core functions instead of their own SQL?▼

Architecture contract D14 makes shared *_core extraction mandatory so tools and HTTP handlers propagate identical semantics. A tool with its own SQL is an automatic review block because it creates a silently diverging surface.

When should I not use this MCP parity skill?▼

Do not use it for why tools share cores or live-role auth (architecture contract), per-tool catalog semantics (api-routes.md), MCP env vars and the write toggle (config skill), running MCP test suites (validation skill), or overall merge gates (change-control skill routes here).

Related Skills

Explore More Software Engineering Skills→
digirati-co-ukdigirati-co-uk
57

routes-site

Standardize site HTTP route handlers in the Madoc TS application.

Official
Intermediate
echoVicechoVic
553

devops/changelog-generation

Generates CHANGELOG entries from git commit history and pipeline artifacts following Conventional Commits.

Community
Intermediate
peppone-choipeppone-choi

verify-implementation

Execute sequential verification checks for project implementation parity and standards.

Community
Advanced
rockcookiesrockcookies
1

why

Investigate design rationale behind code by querying git history and MCP evidence sources.

Community
Advanced