I've learned while building MCP-based tools is that compatibility issues usually don't come from the protocol itself, but from slightly different interpretations between clients and servers.
Having an automated compliance checker should make upgrading MCP versions much less painful.
Thank you. This was my intention indeed, and this tool comes in 2 flavours: fully automated python on npm package for developers, or also a web ui - mcpscore.dev - where everybody can check any mcp server.
I've learned while building MCP-based tools is that compatibility issues usually don't come from the protocol itself, but from slightly different interpretations between clients and servers.
Having an automated compliance checker should make upgrading MCP versions much less painful.
Thank you. This was my intention indeed, and this tool comes in 2 flavours: fully automated python on npm package for developers, or also a web ui - mcpscore.dev - where everybody can check any mcp server.
Looking forward to any feedback!