LION Trend Intent MCP
io-github-lionmaster20-lion-mcp declares 5 capabilities across 5 tools, with 3 critical issues.
Issues
5 of 5 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.
1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.
5 of 5 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.
5 of 5 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.
3 tools can modify data and declare no limit.
1 tool can read data and declares no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
lion_trend_intent_signal_json | write |
assumed |
lion_trend_intent_signal_csv | write |
assumed |
lion_base_dex_signals_json | write |
assumed |
lion_adaptive_data_query | read |
inferred |
lion_payment_attempt_readiness_audit | pay |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.