in.co.buildwright/compliance
in-co-buildwright-compliance 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.
1 tool can modify data and declares no limit.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
mca_late_fee | read |
declared |
compliance_calendar | read |
declared |
company_lookup | read |
declared |
cheque_bounce_timer | read |
declared |
msme_interest | read |
declared |
list_free_tools | read |
declared |
engage_buildwright | read |
declared |
list_services | read |
declared |
request_service | write |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.