Corruptópolis
io-github-portuno-corruptopolis declares 9 capabilities across 9 tools, with 1 critical issue. 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.
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.
8 tools can modify data and declare no limit.
1 tool can read data and declares no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
corruptopolis_entrar | write |
assumed |
corruptopolis_empezar | write |
assumed |
corruptopolis_accion | write |
inferred |
corruptopolis_informe | write |
assumed |
corruptopolis_ranking | write |
assumed |
corruptopolis_yo | write |
assumed |
corruptopolis_perfil | read |
inferred |
corruptopolis_reliquias | write |
assumed |
corruptopolis_autor | write |
assumed |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.