MCP server list / LION - Trend Intent MCP + Marketplace Visibility Audit
x402-paid MCP data: trend feed + visibility audit. USDC/Base. No API key. No PII.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 436.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 370 ms.
- Address
- https://gleaming-cassata-d41682.netlify.app/
api/ mcp?registry=domain_v1_1 - Listed in:
- official MCP registry
mcp_registry - Registry name
- app.netlify.gleaming-cassata-d41682/
lion-mcp - Transport
- streamable HTTP
streamable-http - Host
gleaming-cassata-d41682.netlify.app
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- lion-trend-intent-mcp
- Version:
- 0.4.0
- MCP features it lists:
- tools
- Tool names:
lion_trend_intent_signal_jsonlion_trend_intent_signal_csvlion_base_dex_signals_jsonlion_adaptive_data_querylion_payment_attempt_readiness_audit- Instructions excerpt:
- LION exposes x402-paid MCP/data services on Base. Five tools: (1) lion_trend_intent_signal_json and (2) lion_trend_intent_signal_csv return hardware-wallet buyer-intent + self-custody onboarding-friction intelligence ($0.01 USDC on Base mainnet); (3) lion_base_dex_signals_json is a live Base DEX market-data feed ($0.005 USDC on Base eip155:8453) returning …
Reported Aug 17, 2026, 05:09 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 164 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 519 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 503 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 370 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.