The MCP tools catalog lists 51 tools; the server registers 52

[beyondnetPeru]

reference/core/foundations/common-rules/ai-augmented/03-tools-catalog/evolith-mcp-tools.md
lists 51 MCP tools. The server registers 52.

The file has not been regenerated since 2026-07-31.

Verify it yourself

# rows in the stale catalog
grep -cE '^\| `?evolith-' reference/core/foundations/common-rules/ai-augmented/03-tools-catalog/evolith-mcp-tools.md

# tools the server actually registers
grep -rhoE "name: '(evolith-[a-z0-9-]+)'" src/packages/mcp-server/src/tools/*.ts | sort -u | wc -l

51 and 52.

The fix

Find which tool is missing and add its row, matching the shape of the surrounding rows. The
authoritative list is the generated catalog at
src/sdk/cli/src/commands/api/api.catalog.generated.ts, which is produced from a live boot of
the server — trust it over any hand-written list, this one included.

Done when

Both numbers agree, and the new row names the same tool the generated catalog does.

---

What is not your problem

This repository runs a large number of governance checks against itself. If one goes red on
your PR for a reason unrelated to your change, say so in a comment and a maintainer will sort
it out — do not try to fix the harness to get green. Specifically not yours: anything under
.harness/scripts/ci/ reporting on the gap board, ADR registry, maturity or coverage floors;
Governance guards; release-pipeline and provenance failures; and bilingual findings on
documents outside the sixteen-file entry surface (ADR-0126).

New here? CONTRIBUTING.md has the setup. Short version: fork, npm install,
npm run build. Commits need a Signed-off-by line — git commit -s, and a hook adds it if
you forget.