modelcontextprotocol / modelcontextprotocol/conformance
Add conformance scenario: notifications/cancelled
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 127
- Forks
- 101
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
The spec defines cancellation semantics (notifications/cancelled) with clear MUST/SHOULD requirements, but no conformance scenario exists to validate server behavior.
Proposed checks:
- Server remains stable after receiving cancellation for an unknown request ID (MUST handle gracefully)
- Server handles cancellation of an in-progress request without degradation (SHOULD stop processing)
- Server remains stable under rapid cancellation notification bursts
The scenario requires test servers to expose a slow tool (5+ seconds) to allow cancellation to arrive during processing.
I'll submit a PR for this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing conformance scenarios and test-server setup for notifications and long-running tools. Add a notifications/cancelled scenario covering unknown request IDs, cancellation during a 5+ second tool, and rapid cancellation bursts; done means the server remains stable and the in-progress case checks the expected cancellation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100