Skip to content

fix(python): size MCP tool-call timeouts from accept maxTimeoutSeconds - #21

Closed
PhilBot402 wants to merge 1 commit into
mainfrom
philbot-py-mcp-tool-timeout-38f4
Closed

PhilBot402 wants to merge 1 commit into
mainfrom
philbot-py-mcp-tool-timeout-38f4

Conversation

@PhilBot402

Copy link
Copy Markdown
Owner

Port of x402-foundation#3430 from TypeScript to Python SDK.

Python x402MCPSession and the MCP client wrappers now size paid tool-call timeouts from the accept's maxTimeoutSeconds (default 300s). The initial 402 probe uses a 300s ceiling unless the caller passes read_timeout_seconds. Slow-finality settlements no longer abort at the Python MCP SDK's 60s default. Related to x402-foundation#3439. This change does not close that issue, which also tracks a separate Go port and Bazaar routeTemplate drift.

AI disclosure: Automated by @phdargen. Use your own judgement

Open in Web Open in Cursor 

Paid MCP tool calls wait for the accept's maxTimeoutSeconds (default 300s).
The initial 402 probe uses a 300s ceiling unless the caller sets
read_timeout_seconds.

Co-authored-by: phdargen <phdargen@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant