Would you use an MCP tool that flags breaking API/SDK changes before codegen?

[masem1899]

Hi,

quick question: how much effort did the MCP spec revision from July 28 (sessions gone, new Multi Round-Trip mechanism) or the SDK v1→v2 migration cause you? I'm currently evaluating an idea — an MCP tool that checks breaking changes between two API/SDK versions and delivers migration notes instead of a raw changelog.

If this is relevant for you, 2 minutes in writing would help a lot:

1. How much effort did the spec revision / SDK migration actually cause?
2. Is version-current docs enough (Context7/Deepcon style), or do you need the explicit diff plus migration notes?
3. MCP tool call, or CI check/schema lockfile (like mcp-diff)?
4. $0.01–0.10 per check plausible, or would you expect a flat price/subscription?

No call needed, written is completely fine — even "not relevant for us" helps.

Thanks,
Mario