Confidence Score: 4/5

This change is safe to merge with a non-blocking test coverage gap, but adding analytics-enabled schema coverage would protect legacy MCP compatibility.

Findings

1.  Cover telemetry schemas ▶

### Issue 1
apps/server/src/mastra/mcp/external/deprecated-record-shims.ts:46
The explicit `telemetry` property prevents analytics from adding nested telemetry fields to these deprecated tool schemas, but no regression test covers an analytics-enabled MCP server. A dependency or schema-conversion change could silently expose `telemetry.agent_thinking` and `telemetry.user_intent` again or break legacy shim calls, increasing compatibility support cost. This is non-blocking, but add coverage that lists both shims with analytics enabled, verifies those fields are absent, and validates legacy calls.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This change updates the deprecated MCP record-tool schemas so analytics should leave their telemetry fields untouched, adjusts external MCP configuration loading, and refreshes the JOSE dependency resolution.

T-Rex validation blocked

The analytics-enabled application path could not be exercised because the standalone MCP harness and the analytics package resolved different McpServer module instances. Existing route coverage runs with analytics disabled and does not verify the two deprecated shims’ analytics schemas or legacy calls.

Findings

• Add a regression test for the deprecated record-tool telemetry opt-out before relying on it for compatibility protection.

_{Reviews (1) · Last reviewed commit: "Merge pull request #2831 from CedarCopil..."}