Add C# SDK Tier 1 assessment to SDK listing#2308
Conversation
|
We actually have a follow-up question on the backcompat client conformance tests. We had seen feat: move march back-compat auth tests to optional backcompat suite (modelcontextprotocol/conformance#127) and did not include compatibility with the old 2025-03-26 auth spec (no PRM, OAuth metadata at server root). When running this tiering assessment though, the results flagged those backcompat tests as required for Tier 1. That prompted us to open Add 2025-03-26 OAuth backward compatibility for client conformance (modelcontextprotocol/csharp-sdk#1374). If the back-compat auth tests are not required for Tier 1, we might choose not to merge that PR. We appreciate your guidance on this. Edit: We went ahead and included that back-compat feature in our 1.0.0 release. It looks like the tier skill lost the context of which client conformance tests were required when it was failing to run the tests on Windows and it started working around it by running the client conformance tests differently. Fix Windows compatibility in tier-check client conformance (modelcontextprotocol/conformance#168) |
There was a problem hiding this comment.
Thank you for this submission!
I reviewed the evidence in the issue and verified the conformance suite outcomes on my own machine + looked through the evidence provided for the other requirements.
I had to figure out how to use MCP_CONFORMANCE_SCENARIO in the client to replicate the full test suite with a wrapper, but was able to get full conformance at 100% results on my machine.
I see everything we need to enable a Tier 1 classification - my only ask would be to consolidate the issue content into the main body rather than keep @mikekistler's placeholder if possible.
I.e. to merge the content of @jeffhandley's comment here back into the main issue body that's currently still a placeholder - then we can close and lock the issue for posterity.
felixweinberger
force-pushed
the
jeffhandley/csharp-sdk-tier1
branch
from
4a574b0 to
d3b89d0
Compare
|
@jeffhandley Pushed to this branch to resolve a merge conflict. |
|
Thanks, @felixweinberger! @mikekistler and I got the issue edited too. |
3 participants
Motivation and Context
The C# SDK has v1.0.0 published and all Tier 1 requirements are met. This PR updates the SDK listing page to reflect that assessment with a link to (#2261) C# SDK should be listed as Tier 1 SDK.
How Has This Been Tested?
The mcp-sdk-tier-audit (modelcontextprotocol/conformance) skill was used within Copilot CLI while pointing to the main branch after publishing the 1.0.0 release.
Breaking Changes
N/A
Types of changes
Checklist
Additional context
Closes #2261.