|
| 1 | +# Conformance scenarios not yet passing against the Python SDK on main. |
| 2 | +# CI exits 0 if only these fail, exits 1 on unexpected failures or stale entries. |
| 3 | +# |
| 4 | +# Baseline established against @modelcontextprotocol/conformance pinned in |
| 5 | +# .github/workflows/conformance.yml (CONFORMANCE_VERSION = 0.2.0-alpha.3). |
| 6 | +# New conformance releases are adopted by deliberately bumping that pin and |
| 7 | +# reconciling this file in the same change. |
| 8 | +# |
| 9 | +# Entries are grouped by SEP. As each SEP lands in the SDK the corresponding |
| 10 | +# scenarios start passing and MUST be removed from this list (the runner fails |
| 11 | +# on stale entries), so the baseline burns down per milestone. |
| 12 | + |
| 13 | +client: |
| 14 | + # --- Draft-spec scenarios (in `--suite draft`, also part of `--suite all`) --- |
| 15 | + # SEP-2575 (request metadata / _meta envelope): client does not populate the |
| 16 | + # _meta envelope or the MCP-Protocol-Version header semantics yet. |
| 17 | + - request-metadata |
| 18 | + # SEP-2322 (multi-round-trip requests): client does not echo requestState / |
| 19 | + # handle IncompleteResult yet. |
| 20 | + - sep-2322-client-request-state |
| 21 | + # SEP-2243 (HTTP standardization): no fixture handler / client header support yet. |
| 22 | + - http-custom-headers |
| 23 | + - http-invalid-tool-headers |
| 24 | + # SEP-2106 (JSON Schema $ref handling): client still dereferences network $refs. |
| 25 | + - json-schema-ref-no-deref |
| 26 | + # SEP-2468 (authorization response iss parameter): not implemented in the client. |
| 27 | + - auth/iss-supported |
| 28 | + - auth/iss-not-advertised |
| 29 | + - auth/iss-supported-missing |
| 30 | + - auth/iss-wrong-issuer |
| 31 | + - auth/iss-unexpected |
| 32 | + - auth/iss-normalized |
| 33 | + - auth/metadata-issuer-mismatch |
| 34 | + # SEP-2352 (authorization server migration): client does not re-register when |
| 35 | + # PRM authorization_servers changes. |
| 36 | + - auth/authorization-server-migration |
| 37 | + # SEP-837 (application_type during DCR): the check only fires on draft-version |
| 38 | + # runs; this draft scenario is the one place the client still hits it. |
| 39 | + - auth/offline-access-not-supported |
| 40 | + |
| 41 | + # --- Pre-existing scenarios that fail on checks added after conformance 0.1.15 --- |
| 42 | + # SEP-2350 (scope step-up): WARNING-only; the expected-failures evaluator |
| 43 | + # counts WARNINGs as failures. |
| 44 | + - auth/scope-step-up |
| 45 | + # SEP-990 (enterprise-managed authorization extension): no fixture handler / |
| 46 | + # client support for the token-exchange + JWT bearer flow. |
| 47 | + - auth/enterprise-managed-authorization |
| 48 | + |
| 49 | +# The `active` suite (30 scenarios / 42 assertions) is fully green against |
| 50 | +# mcp-everything-server. Draft-suite entries are added when the workflow |
| 51 | +# gains a `--suite draft` step. |
| 52 | +server: [] |
0 commit comments