Conformance Track B: stateful HTTP/stdio modes, SEP-2549 absence-assert, remaining MRTR scenarios

Open
#1,653 0 comments 0 reactions 1 assignee View on GitHub

@halter73 is already working on this.

Since Jun 25, 2026.

Assessment

This issue has not been assessed yet.

Description

area-tests enhancement P2

Follow-up from #1610. Extensions to the cross-SDK conformance harness that were out of scope for the PR:

  • Stateful HTTP + stdio conformance modes — the harness currently exercises draft stateless HTTP; add stateful-HTTP and stdio transport modes.
  • Reinstate SEP-2549 absence-assert (upstream conformance PR #310) — was dropped pending the RunContext refactor; restore once that lands.
  • Two skipped MRTR scenarios (tampered-state HMAC validation, capability-check per-request gating) — ✅ Done in #1610 (commit 52f97d4b). The est_input_required_result_tampered_state and est_input_required_result_capabilities ConformanceServer tools are implemented and both input-required-result-tampered-state / input-required-result-capability-check rows now run (14/14 RunMrtrConformanceTest pass against the local compat/conformance-draft build). In-process wire-level regressions added in MrtrProtocolTests.
  • Upstream server/discover standalone scenario — file/track an upstream conformance-repo issue for the missing standalone scenario so we can cover the server/discover path end-to-end.

cc #1610

Dominant language
C#
Stars
4.5k
Forks
814
Avg merge
9d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/csharp-sdk

All issues in modelcontextprotocol/csharp-sdk

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.