What LION - Trend Intent MCP + Marketplace Visibility Audit MCP server does
LION - Trend Intent MCP + Marketplace Visibility Audit MCP server exposes two stated data capabilities through MCP: a trend feed and a marketplace visibility audit. The available description labels the data as x402-paid, identifies USDC on Base as the payment currency and network, and states that an API key is not required.
The listing does not provide a README or detailed schema. As a result, the available material does not define the fields returned by the trend feed, the marketplace sources included in an audit, or the exact criteria used to measure visibility. Treat the server as a fit for those broad data needs, but verify response details from the linked project before building production workflows.
How it works
LION - Trend Intent MCP + Marketplace Visibility Audit MCP server is described as an MCP data service with x402-based payment. Requests therefore use the payment model specified by the listing rather than an API-key credential. The stated payment details are USDC on Base.
The supplied material does not identify the MCP transport, installation command, request format, tool names, response schema, or payment configuration steps. It also does not name a required client. Those details must be confirmed from the linked project or its runtime documentation before implementation.
Tools and capabilities
The available listing supports these capabilities:
- Retrieve data from a trend feed.
- Run or access a marketplace visibility audit.
- Pay for MCP data through x402 using USDC on Base.
- Operate without an API key, according to the listing.
- Use the service without providing PII, according to the listing.
The phrase “trend intent” appears in the project name, while the description specifically identifies a trend feed. No further explanation is available about how intent is derived, how trends are ranked, or what marketplace visibility metrics are returned.
Limitations and notes
LION - Trend Intent MCP + Marketplace Visibility Audit MCP server has limited published documentation in the supplied material. There is no available README, so client compatibility, transport support, installation, environment variables, tool schemas, rate limits, pricing details beyond the x402 payment reference, and error behavior cannot be confirmed here.
The listing says that no API key and no PII are required. That does not establish broader data-retention, privacy, or security policies, which are not described. The use of USDC on Base also identifies the stated payment setup, but the material does not explain wallet configuration, transaction handling, balances, or network requirements.
Before adoption, confirm the current endpoint, supported MCP clients, payment flow, returned data structures, and audit scope from the project at the supplied URL.