Recta
io-github-rectabuild-recta 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.
1 tool is classified as irreversible and declares 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.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
recta_about | read |
declared |
recta_status | read |
declared |
recta_service_descriptor | read |
declared |
recta_fit_check | read |
declared |
recta_saving_odds | read |
declared |
recta_request_template | read |
declared |
recta_trial_evaluation | read |
declared |
recta_prepare_signed_request | read |
declared |
recta_send_signed_request | send |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.