Commonstop: Shared-route sharps and red-bag pickup for Dallas County offices
com-forevenza-services-commonstop declares 7 capabilities across 7 tools, with 3 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
7 of 7 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 classified as irreversible or destructive and declare no limit. 1 of them is counted only because the server annotated it destructiveHint. 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.
1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.
7 of 7 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.
7 of 7 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.
2 tools can modify data and declare no limit.
3 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
describe_business | read |
declared |
submit_request | write |
inferred |
request_status | read |
declared |
inspect_offer | read |
declared |
accept_offer | write |
assumed |
decline_offer | destructive |
declared |
release_payment | pay |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.