Title: Exercise the SEP-2575 stateless probes and SEP-2243 resource/prompt headers in the conformance fixtures by maxisbey · Pull Request #3442 · modelcontextprotocol/python-sdk · GitHub
Open Graph Title: Exercise the SEP-2575 stateless probes and SEP-2243 resource/prompt headers in the conformance fixtures by maxisbey · Pull Request #3442 · modelcontextprotocol/python-sdk
X Title: Exercise the SEP-2575 stateless probes and SEP-2243 resource/prompt headers in the conformance fixtures by maxisbey · Pull Request #3442 · modelcontextprotocol/python-sdk
Description: Two conformance scenarios were green against this SDK without measuring anything. This gives the everything-server the two diagnostic tools server-stateless probes by name, makes the conformance client's http-standard-headers handler round-trip a resource and a prompt as well as a tool, and (separate commit) renames examples/clients/simple-chatbot/README.MD to the README.md its pyproject declares so the workspace builds with --all-packages on case-sensitive filesystems. Motivation and Context server-stateless. Its sep-2575-http-server-no-independent-requests-on-stream and sep-2575-server-no-log-without-loglevel checks call tools named test_streaming_elicitation and test_logging_tool (stateless.ts). Our fixture had neither. MCPServer answers an unknown tool with an isError: true CallToolResult — a result frame — so the harness's not-testable guard (which only fires when every frame is a JSON-RPC error) never tripped, and both checks passed on "Unknown tool". typescript-sdk's fixture carries the pair (everythingServer.ts). Rather than a tool that just returns text (which is byte-identical on the wire to the unknown-tool result), test_streaming_elicitation is a tool that genuinely needs elicitation, asked through a Resolve(...) dependency. On 2026-07-28 the SDK returns the question as an InputRequiredResult instead of putting elicitation/create on the response stream — which is the behaviour the check enforces — on 2025-11-25 it is a mid-call elicitation, and with no declared elicitation capability it is rejected with -32021. So the probe now sits on the SDK's version branch rather than beside it. test_logging_tool logs once on the request-scoped channel, so what the second check observes is the per-request logLevel gate. http-standard-headers. The scenario reports any of tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get the client never sends as SKIPPED rather than failed. Our handler only listed and called a tool, so the Mcp-Method / Mcp-Name checks for resources and prompts were never judged. It now also reads the first resource and gets the first prompt. README case. hatchling validates project.readme before building any target, so uv sync --all-packages / uv build --all-packages failed on Linux with OSError: Readme file does not exist: README.md. The conformance runner's built-in python-sdk config works around exactly this with two targeted syncs (known-sdks.ts). How Has This Been Tested? Against conformance 0.2.0-alpha.11 locally, through run-server.sh / run-client.sh: server-stateless at --spec-version 2026-07-28: 30/30, both SEP-2575 checks SUCCESS on real results. Direct POSTs to the 2026-07-28 entry: test_streaming_elicitation with elicitation declared → 200, single application/json result with resultType: "input_required" and the elicitation/create embedded in inputRequests; with empty capabilities → 400 -32021 with requiredCapabilities.elicitation. test_logging_tool emits no notifications/message without _meta["io.modelcontextprotocol/logLevel"], exactly one with logLevel: "debug". In-memory Client(mode="legacy") and Client(mode="auto") both complete the tool via the elicitation callback. http-standard-headers at 2026-07-28: 3 SUCCESS / 8 SKIPPED → 9 SUCCESS / 2 SKIPPED (the remaining two are initialize / notifications/initialized, which a 2026-07-28 client never sends). All six CI legs: server 84/0 · 151/0 · 204/25 (the nine tasks-*, expected); client 224/0 · 387/0 · 464/9 (the nine per-check DPoP/WIF, expected). The client totals are +6 each versus main from the header checks moving out of SKIPPED; no baseline changes. uv build --package mcp-simple-chatbot fails before the rename with the OSError above and succeeds after. ruff, pyright, and the markdownlint hook on the renamed file are clean. Breaking Changes None. Conformance fixtures and an example's file name only. 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 test_logging_tool uses the deprecated request-scoped ctx.info (SEP-2577) on purpose — there is no non-deprecated channel and the check exists to exercise that gate — with the same reportDeprecated suppression the file already carries for test_tool_with_logging and test_reconnection. The reason these checks went vacuous rather than "not testable" is that MCPServer reports an unknown tool as an isError result instead of a JSON-RPC error; any future name-probed harness fixture we lack will be masked the same way. Not changed here. Once this lands the conformance repo's python-sdk runner entry can go back to uv sync --frozen --all-extras --all-packages. v1.x carries the same README.MD, so the python-sdk-v1 entry's --all-packages build has the same problem there; the rename is its own commit in case a [v1.x] backport is wanted. On a case-insensitive filesystem an existing checkout may keep showing the old casing until re-cloned; git tracks the new name either way. AI Disclaimer
Open Graph Description: Two conformance scenarios were green against this SDK without measuring anything. This gives the everything-server the two diagnostic tools server-stateless probes by name, makes the conformance cl...
X Description: Two conformance scenarios were green against this SDK without measuring anything. This gives the everything-server the two diagnostic tools server-stateless probes by name, makes the conformance cl...
Opengraph URL: https://github.com/modelcontextprotocol/python-sdk/pull/3442
X: @github
Domain: github.com
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /:user_id/:repository/pull/:id/files(.:format) |
| route-controller | pull_requests |
| route-action | files |
| fetch-nonce | v2:4348c9ba-1e44-9263-f5d6-afa1a3d74ecc |
| current-catalog-service-hash | ae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b |
| request-id | DE50:E3C4F:142A0B2:19B5549:6B012C2D |
| html-safe-nonce | 8ad096cf28ca872f467ec9c3e09cf6b6ae6aa187d8d25734c6040bca36b416e9 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJERTUwOkUzQzRGOjE0MkEwQjI6MTlCNTU0OTo2QjAxMkMyRCIsInZpc2l0b3JfaWQiOiIzNDQzNDM3NjQ4OTE5Mzc4MzciLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 32ee004d7b7008ed9fd096a04708af57d6a8918d2010489a13be05b608a5dab1 |
| hovercard-subject-tag | pull_request:4444202623 |
| github-keyboard-shortcuts | repository,pull-request-list,pull-request-conversation,pull-request-files-changed,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/modelcontextprotocol/python-sdk/pull/3442/files |
| twitter:image | https://avatars.githubusercontent.com/u/224885523?s=400&v=4 |
| twitter:card | summary_large_image |
| og:image | https://avatars.githubusercontent.com/u/224885523?s=400&v=4 |
| og:image:alt | Two conformance scenarios were green against this SDK without measuring anything. This gives the everything-server the two diagnostic tools server-stateless probes by name, makes the conformance cl... |
| og:site_name | GitHub |
| og:type | object |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| diff-view | unified |
| go-import | github.com/modelcontextprotocol/python-sdk git https://github.com/modelcontextprotocol/python-sdk.git |
| octolytics-dimension-user_id | 182288589 |
| octolytics-dimension-user_login | modelcontextprotocol |
| octolytics-dimension-repository_id | 862584018 |
| octolytics-dimension-repository_nwo | modelcontextprotocol/python-sdk |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 862584018 |
| octolytics-dimension-repository_network_root_nwo | modelcontextprotocol/python-sdk |
| turbo-body-classes | logged-out env-production page-responsive full-width |
| disable-turbo | true |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width