Observed arrival · 2026-11-18
MCP Write-Safety Requirements: testing risky writes
An open-source draft standard and preview toolkit for checking whether MCP servers create, change, or delete data as requested.
- For
- MCP server developers testing data-writing tools
- Worth noticing
- The preview tests 14 requirements fully and 23 partially, explicitly marking the remaining coverage as untested.
Field notes
The page groups requirements by write-safety concern and links individual requirement pages, a decision log, discussion, CLI coverage notes, a GitHub Action README, and TypeScript and Python kits. Its sample run uses tiny-tracker in memory at 127.0.0.1; output separates held, violated, self-attested, and not-tested results. The page reports an audit of GitHub MCP server v2.1.0 with lost updates in 19 of 30 concurrent issue_write pairs; that figure is the site's account.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue