io.github.wsmhj/stivio-mcp
io-github-wsmhj-stivio-mcp declares 6 capabilities across 6 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
6 of 6 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is annotated by the server as destructive (destructiveHint) and declares no limit. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.
6 of 6 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
6 of 6 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
1 tool can modify data and declares no limit.
4 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
list_video_models | read |
declared |
estimate_video_cost | read |
declared |
get_credit_balance | read |
declared |
upload_image | write |
inferred |
generate_video | destructive |
declared |
get_video_status | read |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.