17TRACK MCP by usefulapi
io-usefulapi-17track declares 9 capabilities across 9 tools, with 2 critical issues.
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.
6 tools are classified as irreversible and declare no limit.
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.
3 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
track17_get_quota | read |
declared |
track17_list_tracking_numbers | read |
declared |
track17_get_tracking | read |
declared |
track17_realtime_lookup | destructive |
declared |
track17_register_numbers | destructive |
declared |
track17_change_carrier | destructive |
declared |
track17_change_tag | destructive |
declared |
track17_stop_tracking | destructive |
declared |
track17_retrack | destructive |
declared |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.