com.usefreebox/freebox
com-usefreebox-freebox declares 9 capabilities across 9 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
9 of 9 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.
2 tools are annotated by the server as destructive (destructiveHint) and declare 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.
9 of 9 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.
9 of 9 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.
6 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
find_free_stuff | read |
declared |
area_summary | read |
declared |
my_vault | read |
declared |
my_alerts | read |
declared |
save_to_vault | read |
inferred |
remove_from_vault | destructive |
declared |
create_alert | write |
inferred |
delete_alert | destructive |
declared |
create_ebay_listing | read |
declared |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.