Question: would MCP release validation be useful for this server?

[daranium2020]

Hi, I found this MCP server and wanted to ask a quick question.

I’m building MCP Release, a small release checker for MCP servers. It checks MCP initialization, tool discovery, schemas, and basic tool behavior before release.

You can try it with any public HTTPS MCP endpoint here:
https://mcprelease.dev

For local, private, staging, or authenticated MCP servers, it can also run from CLI:

npx -y @mcp-release/cli check

It also works inside GitHub Actions:

• uses: daranium2020/mcp-release@v0.1.2
  with:
  endpoint: https://your-mcp-server.example.com/mcp

Repo:
https://github.com/daranium2020/mcp-release

I’m trying to understand what checks real MCP server maintainers would actually find useful.

Would a release check like this be useful for this project’s workflow?
And what MCP-specific checks would be missing for a server like this?

No action required - mainly looking for feedback from MCP server maintainers.

Thank you!

[DeusData]

Thanks for asking and for explaining the project.

Release validation is useful, but codebase-memory-mcp is a local stdio server rather than a public HTTPS MCP endpoint. We would not introduce a hosted validation service, API key, or external release dependency into the project.

The checks most relevant to a local server like this are correct stdio framing, a clean stdout channel, initialization and protocol negotiation, tool list and schema validation, malformed parameter handling, bounded responses, repeated calls, offline startup, and clean process shutdown.

We are happy to offer that feedback, but any release gate adopted by this project needs to remain local, auditable, and runnable inside our existing CI without depending on an external service.