Orbylon
com-orbylon-readiness 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.
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.
1 tool can modify data and declares no limit.
7 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
scan_business_readiness | read |
declared |
find_businesses | read |
declared |
lookup_business | read |
declared |
list_business_offerings | read |
declared |
place_order | destructive |
declared |
get_order_status | read |
declared |
request_quote | write |
inferred |
list_business_paid_endpoints | read |
declared |
check_business_token | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-16 | 22 | tools/list on https://orbylon.com/api/mcp, published in the official MCP registry as com.orbylon/readiness 1.5.0 |
| 2026-10-11 | 22 | tools/list on https://orbylon.com/api/mcp, published in the official MCP registry as com.orbylon/readiness 1.5.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.