Observed arrival · 2026-11-19
MCP Write-Safety Requirements
A draft standard and preview test tools for checking whether MCP servers handle data-changing operations safely.
○Open
⊠Login
$Paid
†Ads
✦Pretty
●Pro
◎Niche
◉Human
⚑Risk
ƒJS
- For
- MCP server developers and reviewers
- Worth noticing
- The sample runs on 127.0.0.1 in memory; the page warns that full-mode checks can make real writes.
Field notes
The CLI demo uses tiny-tracker, a sample server with deliberate defects, and prints a verdict for each requirement; the report keeps a row for every write path rather than collapsing results into a single score. The page illustrates stale-version handling and reports an audit in which concurrent GitHub MCP issue writes lost a change in 19 of 30 pairs, compared with 0 of 28 in GitHub’s per-field update. The specification is labeled Draft 0.9 for public comment.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
○OpenPublic substance visible
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use
ƒJavaScriptBrowser-side code central
One card from the complete issue