Anthropic MCP directory: required tool annotations and manifest version?
In November 2025 Anthropic reviewed Windows-MCP (CursorTouch/Windows-MCP) for its MCP directory and required tool annotations (readOnlyHint, destructiveHint), plus recommended manifest_version "0.3" and expanded security documentation. The maintainer's latest manifest.json still showed "0.2", so is 0.2 acceptable or must every tool be annotated before resubmitting?
Originally asked on GitHub: https://github.com/CursorTouch/Windows-MCP/issues/58
4 answers
The issue is closed as completed: after the review, the maintainer made a new submission and the thread was closed. The thread does not say whether that resubmission passed review.
What the review asked for:
- Required — every tool in the schema must carry annotations such as readOnlyHint and destructiveHint.
- Recommended — set manifest_version to "0.3" in manifest.json.
- Recommended — expand the README security section to cover PowerShell command execution risks and the FAILSAFE configuration.
On the manifest version: the maintainer reported that the latest manifest.json still showed "0.2". A contributor replied that "0.2" can be used if you are having issues packing. The thread does not explain what packing issue prompted that advice or whether "0.3" was tried.
Practical takeaway from the thread: treat the tool annotations as the mandatory part of the review, add the security documentation, and try packing with the manifest version your tooling supports — "0.2" is acceptable per the contributor if packing fails.
Security note: keep readOnlyHint/destructiveHint accurate and document PowerShell execution risks and FAILSAFE, since the reviewer explicitly flagged them.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
Anthropic's directory review required tool annotations (readOnlyHint, destructiveHint), recommended manifest_version "0.3", and recommended expanding the README security section on PowerShell execution risks and FAILSAFE.
Source: https://github.com/CursorTouch/Windows-MCP/issues/58 (opens external site)
Did this work for you?What @Jeomon tried on GitHub (Outcome unclear)
The maintainer checked the latest manifest.json and found it still showed manifest version "0.2", which raised the packing question.
Source: https://github.com/CursorTouch/Windows-MCP/issues/58#issuecomment-3579046169 (opens external site)
Did this work for you?What @bryan-anthropic tried on GitHub (Outcome unclear)
A contributor said "0.2" can be used if there are issues packing; the maintainer then made a new submission and the issue was closed as completed. The thread does not confirm whether the resubmission passed review.
Source: https://github.com/CursorTouch/Windows-MCP/issues/58#issuecomment-3589491442 (opens external site)
Did this work for you?
Related questions
- Windows-MCP State-Tool fails with 'Taskbar' error – correct install method?
- Windows-MCP State-Tool fails with 'Taskbar' error on German Windows 11 — how to fix?
- How to fix Windows-MCP State-Tool vision error 'Tool result is too large. Maximum size is 1MB' on 2560x1440?
- Windows-MCP times out MCP initialize handshake with Claude Desktop (-32001) on cold start
- Windows-MCP fails on Microsoft Store Claude Desktop with egg_base error from ${__dirname} path. How to fix?