Skip to content

C10: Add parser disagreement and intermediary integrity controls#201

Merged
jmanico merged 1 commit intomainfrom
feat/c10-parser-disagreement-controls
Mar 17, 2026
Merged

C10: Add parser disagreement and intermediary integrity controls#201
jmanico merged 1 commit intomainfrom
feat/c10-parser-disagreement-controls

Conversation

@jmanico
Copy link
Copy Markdown
Member

@jmanico jmanico commented Mar 17, 2026

Summary

  • 10.3.5 (L2): Prevent protocol downgrade via Mcp-Protocol-Version header stripping on streamable-HTTP transports
  • 10.4.7 (L2): Reject JSON-RPC messages with duplicate keys at any nesting level — motivated by CVE-2017-12635 (CouchDB, CVSS 9.8) and CVE-2020-16250 (Vault auth bypass)
  • 10.4.8 (L3): Require intermediaries to forward canonicalized representations or reject ambiguous byte representations

Dropped the proposed numeric precision requirement as largely theoretical for current MCP usage.

Closes #182

Test plan

  • Verify requirement numbering is sequential in C10.3 and C10.4
  • Confirm levels are consistent with existing C10 requirements
  • Review wording for testability

Generated with Claude Code

Address issue #182: add three requirements for parser disagreement
and intermediary message integrity in MCP chains.

- 10.3.5 (L2): Prevent protocol downgrade via Mcp-Protocol-Version
  header stripping on streamable-HTTP transports
- 10.4.7 (L2): Reject JSON-RPC messages with duplicate keys at any
  nesting level (motivated by CVE-2017-12635, CVE-2020-16250)
- 10.4.8 (L3): Require intermediaries to forward canonicalized
  representations or reject ambiguous byte representations

Dropped the proposed numeric precision requirement as largely
theoretical for current MCP usage.

Closes #182

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@jmanico jmanico merged commit cbd7ff9 into main Mar 17, 2026
3 checks passed
@jmanico jmanico deleted the feat/c10-parser-disagreement-controls branch March 22, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant