René's URL Explorer Experiment


Title: 2026-07-28 transport rejects client notifications with -32600; real clients send notifications/cancelled (TODO(L57)) · Issue #3324 · modelcontextprotocol/python-sdk · GitHub

Open Graph Title: 2026-07-28 transport rejects client notifications with -32600; real clients send notifications/cancelled (TODO(L57)) · Issue #3324 · modelcontextprotocol/python-sdk

X Title: 2026-07-28 transport rejects client notifications with -32600; real clients send notifications/cancelled (TODO(L57)) · Issue #3324 · modelcontextprotocol/python-sdk

Description: Summary On the 2026-07-28 per-request-envelope path, the streamable-HTTP transport rejects any client notification with HTTP 400 and -32600 "Body must be a single JSON-RPC request object". The same notification is accepted with 202 on th...

Open Graph Description: Summary On the 2026-07-28 per-request-envelope path, the streamable-HTTP transport rejects any client notification with HTTP 400 and -32600 "Body must be a single JSON-RPC request object". The same...

X Description: Summary On the 2026-07-28 per-request-envelope path, the streamable-HTTP transport rejects any client notification with HTTP 400 and -32600 "Body must be a single JSON-RPC request object"...

Opengraph URL: https://github.com/modelcontextprotocol/python-sdk/issues/3324

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"2026-07-28 transport rejects client notifications with -32600; real clients send notifications/cancelled (TODO(L57))","articleBody":"### Summary\n\nOn the `2026-07-28` per-request-envelope path, the streamable-HTTP transport rejects **any** client notification with HTTP 400 and `-32600 \"Body must be a single JSON-RPC request object\"`. The same notification is accepted with `202` on the handshake era.\n\n`mcp/server/_streamable_http_modern.py:349-362` documents this as a deliberate choice, and notes the decision is still open:\n\n```python\nexcept ValidationError:\n    # Well-formed JSON that isn't a single request object. The transport\n    # spec permits notification POSTs and gives the server two responses\n    # (202 accept / 4xx cannot-accept; streamable-http §Sending Messages\n    # item 5). The core protocol defines no client→server notifications\n    # over HTTP at 2026-07-28 (cancellation is SSE-stream close), so this\n    # entry takes the cannot-accept branch. TODO(L57): S4 owns the\n    # strict-vs-lenient choice.\n```\n\n**I'm not reporting a spec violation** — the transport spec permits either branch, and the reasoning above is sound. I'm supplying the empirical input that `TODO(L57)` is missing: **real clients do send notifications on `2026-07-28`**, so the strict branch produces a steady stream of 400s in production.\n\n### Observed in production\n\nA server running `mcp==2.0.0` behind an OAuth-protected streamable-HTTP endpoint, serving live `Claude-User` connector traffic. Within one client session, on `2026-07-28`:\n\n| Method | Result |\n|---|---|\n| `server/discover` | 200 |\n| `notifications/cancelled` | **400** `-32600` |\n| `tools/list` (234 ms later) | 200 |\n\nThe client was unaffected — notifications are fire-and-forget, so it carried on and the next request succeeded. The practical cost is observability rather than function: a monitoring rule of the obvious shape (\"no 400s on the new revision\") fires permanently, and the 400s are indistinguishable by status code from genuine protocol failures.\n\n### Reproduction\n\nDepends only on `mcp` and `httpx`; no network.\n\n```python\nimport anyio, httpx\nfrom mcp.server import MCPServer\nfrom mcp.server.transport_security import TransportSecuritySettings\n\nPV = \"io.modelcontextprotocol/protocolVersion\"\nCC = \"io.modelcontextprotocol/clientCapabilities\"\n\nsrv = MCPServer(name=\"repro\", version=\"0.0.1\")\n\n@srv.tool(name=\"ping\", description=\"noop\")\ndef ping() -> str:\n    return \"pong\"\n\ndef app():\n    return srv.streamable_http_app(\n        stateless_http=True, json_response=True,\n        transport_security=TransportSecuritySettings(enable_dns_rebinding_protection=False),\n    )\n\nasync def post(label, body, version):\n    a = app()\n    async with a.router.lifespan_context(a):\n        async with httpx.AsyncClient(transport=httpx.ASGITransport(app=a), base_url=\"http://localhost\") as c:\n            r = await c.post(\"/mcp\", json=body, headers={\n                \"Accept\": \"application/json, text/event-stream\",\n                \"MCP-Protocol-Version\": version,\n                \"Mcp-Method\": body[\"method\"],\n            })\n            print(f\"{label:\u003c48} HTTP {r.status_code}  {r.text[:100]}\")\n\nasync def main():\n    meta = {PV: \"2026-07-28\", CC: {}}\n    await post(\"notification, WITH _meta envelope\",\n               {\"jsonrpc\": \"2.0\", \"method\": \"notifications/cancelled\",\n                \"params\": {\"requestId\": 1, \"_meta\": meta}}, \"2026-07-28\")\n    await post(\"notification, without _meta envelope\",\n               {\"jsonrpc\": \"2.0\", \"method\": \"notifications/cancelled\",\n                \"params\": {\"requestId\": 1}}, \"2026-07-28\")\n    await post(\"control: request (has id), WITH envelope\",\n               {\"jsonrpc\": \"2.0\", \"id\": 1, \"method\": \"tools/list\",\n                \"params\": {\"_meta\": meta}}, \"2026-07-28\")\n    await post(\"same notification on 2025-11-25\",\n               {\"jsonrpc\": \"2.0\", \"method\": \"notifications/cancelled\",\n                \"params\": {\"requestId\": 1}}, \"2025-11-25\")\n\nanyio.run(main)\n```\n\nOutput:\n\n```\nnotification, WITH _meta envelope                HTTP 400  {\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32600,\"message\":\"Body must be a single JSON-RPC request object\"},\"id\":null}\nnotification, without _meta envelope             HTTP 400  {\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32600,\"message\":\"Body must be a single JSON-RPC request object\"},\"id\":null}\ncontrol: request (has id), WITH envelope         HTTP 200  {\"jsonrpc\":\"2.0\",\"id\":1,\"result\":{...}}\nsame notification on 2025-11-25                  HTTP 202\n```\n\nNote the discriminator is the **absent `id`**, not the envelope: adding a well-formed `params._meta` changes nothing, because `JSONRPCRequest.model_validate` fails before the envelope is ever examined.\n\n### Questions\n\n1. Is the cannot-accept branch intended to stay, now that clients are observably sending these? The lenient branch (`202` and drop) would match handshake-era behaviour for the same message and keep 4xx meaningful as a failure signal.\n2. If it stays, would you consider a distinguishable response — a dedicated error message or code for \"notifications are not accepted on this revision\" — so operators can separate it from genuine protocol errors without parsing bodies?\n3. Is it worth a note in the migration guide? A dual-era server inherits this the moment a client starts using `2026-07-28`, with no change on the server's part.\n\n### Environment\n\n```\npython     3.13.7\nmcp        2.0.0\nmcp-types  2.0.0\nstarlette  1.0.0\npydantic   2.13.4\n```\n","author":{"url":"https://github.com/EsntlSolutions","@type":"Person","name":"EsntlSolutions"},"datePublished":"2026-08-17T13:03:13Z","url":"https://github.com/modelcontextprotocol/python-sdk/issues/3324"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:e39013d6-eaaf-c44f-079c-8e505ac3ef70
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idA44E:33067A:AF8D2:E8658:6B00B9AC
html-safe-noncec0cc65dee83866df8cfea549507f8a58cfd66826042d1298ad5eeae3450b9382
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBNDRFOjMzMDY3QTpBRjhEMjpFODY1ODo2QjAwQjlBQyIsInZpc2l0b3JfaWQiOiIzOTE0Mjk3MzQ5ODQ5MDA0NDYwIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0=
visitor-hmacc247a981b5b014fc917af8c8df31f8f0576f2c666badd36f571483c6502cc78e
hovercard-subject-tagissue:5172171323
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/modelcontextprotocol/python-sdk/3324/issue_layout
twitter:imagehttps://opengraph.githubassets.com/5d4ba366b12aa50bc56adf6e43626e343f11ea6411f32978eed2d39598b94dd2/modelcontextprotocol/python-sdk/issues/3324
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/5d4ba366b12aa50bc56adf6e43626e343f11ea6411f32978eed2d39598b94dd2/modelcontextprotocol/python-sdk/issues/3324
og:image:altSummary On the 2026-07-28 per-request-envelope path, the streamable-HTTP transport rejects any client notification with HTTP 400 and -32600 "Body must be a single JSON-RPC request object". The same...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameEsntlSolutions
hostnamegithub.com
expected-hostnamegithub.com
None1d07c25977adfc5ff6acb0a962a9bc168c07afbda6fef765f9761c350c2ae4a2
turbo-cache-controlno-preview
go-importgithub.com/modelcontextprotocol/python-sdk git https://github.com/modelcontextprotocol/python-sdk.git
octolytics-dimension-user_id182288589
octolytics-dimension-user_loginmodelcontextprotocol
octolytics-dimension-repository_id862584018
octolytics-dimension-repository_nwomodelcontextprotocol/python-sdk
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id862584018
octolytics-dimension-repository_network_root_nwomodelcontextprotocol/python-sdk
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release5429cbfc6aca8c7b9a086a3c8f47400346f38cc9
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/modelcontextprotocol/python-sdk/issues/3324#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmodelcontextprotocol%2Fpython-sdk%2Fissues%2F3324
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmodelcontextprotocol%2Fpython-sdk%2Fissues%2F3324
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=modelcontextprotocol%2Fpython-sdk
Reloadhttps://github.com/modelcontextprotocol/python-sdk/issues/3324
Reloadhttps://github.com/modelcontextprotocol/python-sdk/issues/3324
Reloadhttps://github.com/modelcontextprotocol/python-sdk/issues/3324
modelcontextprotocolhttps://github.com/modelcontextprotocol
python-sdkhttps://github.com/modelcontextprotocol/python-sdk
Codehttps://github.com/modelcontextprotocol/python-sdk
Issues308 (308)https://github.com/modelcontextprotocol/python-sdk/issues
Pull requests112 (112)https://github.com/modelcontextprotocol/python-sdk/pulls
Actionshttps://github.com/modelcontextprotocol/python-sdk/actions
Projectshttps://github.com/modelcontextprotocol/python-sdk/projects
Security and quality12 (12)https://github.com/modelcontextprotocol/python-sdk/security
Insightshttps://github.com/modelcontextprotocol/python-sdk/insights
https://github.com/modelcontextprotocol/python-sdk
New issuehttps://github.com/login?return_to=https://github.com/modelcontextprotocol/python-sdk/issues/3324
New issuehttps://github.com/login?return_to=https://github.com/modelcontextprotocol/python-sdk/issues/3324
#3326https://github.com/modelcontextprotocol/python-sdk/pull/3326
2026-07-28 transport rejects client notifications with -32600; real clients send notifications/cancelled (TODO(L57))https://github.com/modelcontextprotocol/python-sdk/issues/3324#top
#3326https://github.com/modelcontextprotocol/python-sdk/pull/3326
P1Significant bug affecting many users, highly requested featurehttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22P1%22
bugSomething isn't workinghttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22bug%22
spec-2026-07-28Concerns the SDK's implementation of the 2026-07-28 MCP spec revisionhttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22spec-2026-07-28%22
v2Affects the v2 line (2.x on main)https://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22v2%22
https://github.com/EsntlSolutions
EsntlSolutionshttps://github.com/EsntlSolutions
on Aug 17, 2026https://github.com/modelcontextprotocol/python-sdk/issues/3324#issue-5172171323
maxisbeyhttps://github.com/maxisbey
P1Significant bug affecting many users, highly requested featurehttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22P1%22
bugSomething isn't workinghttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22bug%22
on Aug 17, 2026https://github.com/modelcontextprotocol/python-sdk/issues/3324#event-29565518731
https://github.com/Ben-Home
Ben-Homehttps://github.com/Ben-Home
on Aug 17, 2026https://github.com/modelcontextprotocol/python-sdk/issues/3324#issuecomment-5316990665
maxisbeyhttps://github.com/maxisbey
completedhttps://github.com/modelcontextprotocol/python-sdk/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#3326https://github.com/modelcontextprotocol/python-sdk/pull/3326
on Aug 17, 2026https://github.com/modelcontextprotocol/python-sdk/issues/3324#event-29579918810
claudehttps://github.com/apps/claude
v2Affects the v2 line (2.x on main)https://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22v2%22
spec-2026-07-28Concerns the SDK's implementation of the 2026-07-28 MCP spec revisionhttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22spec-2026-07-28%22
on Sep 30, 2026https://github.com/modelcontextprotocol/python-sdk/issues/3324#event-32187835897
Sign up for freehttps://github.com/signup?return_to=https://github.com/modelcontextprotocol/python-sdk/issues/3324
Sign in to commenthttps://github.com/login?return_to=https://github.com/modelcontextprotocol/python-sdk/issues/3324
P1Significant bug affecting many users, highly requested featurehttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22P1%22
bugSomething isn't workinghttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22bug%22
spec-2026-07-28Concerns the SDK's implementation of the 2026-07-28 MCP spec revisionhttps://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22spec-2026-07-28%22
v2Affects the v2 line (2.x on main)https://github.com/modelcontextprotocol/python-sdk/issues?q=state%3Aopen%20label%3A%22v2%22
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.