Fix timeout reset upon progress notification

[lowlyocean]

Motivation and Context

Closes #2816

How Has This Been Tested?

Ran the full test suite

Breaking Changes

No breaking changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

This fixes MCP inspector v2, which claims to automatically reset request timeout when progress notifications are received

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8e1043a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@2817

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2817

@modelcontextprotocol/core

npm i https://pkg.pr.new/@modelcontextprotocol/core@2817

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@2817

@modelcontextprotocol/server-legacy

npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2817

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@2817

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@2817

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@2817

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@2817

commit: 8e1043a

[koriyoshi2041]

The startTime reset here changes maxTotalTimeout from an absolute request lifetime cap into another inactivity window. That is why all 12 protocol:timeout:max-total E2E variants time out in Node 20/22/24: recurring progress can now postpone the maximum indefinitely. The inactivity timer already resets via clearTimeout + setTimeout; startTime needs to remain the original request timestamp. Please remove the info.startTime = Date.now() assignment and keep/add a regression where progress extends the ordinary timeout but the request still rejects at the original maxTotalTimeout deadline.