Fix stale MCP tool-count references (78/81 -> 84)#361
Open
unggulyoga-prog wants to merge 1 commit into
Open
Conversation
Docs and the server instructions string cited outdated tool counts (78 in README/RESEARCH/server.js, 81 in CLAUDE.md). Verified the current count via grep across src/tools/*.js: 84 registered tools.
This was referenced Jul 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
server.tool(registrations across all files insrc/tools/*.js: 84 tools.Left
src/cli/index.js's "70 MCP tools accessible via CLI" comment untouched — that's a different metric (CLI command/subcommand coverage), not total MCP tool count, and I didn't want to guess at that number without verifying it separately.Test plan
npm run lint— no new warnings introduced (pre-existing warnings in unrelated files)npm run test:unit— same 2 pre-existing failures before and after this change (network-dependent Pine compile tests + a pre-existing Windows path bug insanitization.test.js), confirmed viagit stashcomparison