Issues in MCP implementation #2692

Version

codebase-memory-mcp 0.12.1

Platform

macOS (Apple Silicon)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

Hey,

Ran codebase-memory-mcp 0.12.1 through mcpscore (https://mcpscore.dev/). It's in really good shape: complete tool annotations, prompts and output schemas, a clean security scan, and helpful hints on bad arguments!

A few things still to fix:

1. list_projects accepts wrong-typed args without complaint ({"format":123,"detail":"bogus"} succeeds). The other tools reject these.
2. An invalid cursor on tools/list / prompts/list returns an empty page instead of -32602, so a client concludes there are no tools.
3. Unknown tool names come back as isError results; the spec treats them as a protocol error (-32602).
4. 103 tool parameters have no description (e.g. most of search_graph's 19). For agents, that's the highest-value fix.
5. Small: tool titles, and serverInfo.title / websiteUrl (already in your server.json).

Reproduction

if codebase-memory-mcp is installed and on your PATH:

uvx mcpscore --smoke --stdio codebase-memory-mcp

Without installing it, through the npm package the registry lists:

uvx mcpscore --smoke --stdio npx -y codebase-memory-mcp

Logs

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.