LION Trend Intent MCP
REMOTE · GLEAMING-CASSATA-D41682.NETLIFY.APP · SCANNED SEP 25
Read-only x402-paid trend-intent MCP tools for JSON and CSV signals.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1462 tokens (~292/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the LION Trend Intent MCP server?
LION Trend Intent MCP is a hosted endpoint at https://gleaming-cassata-d41682.netlify.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gleaming-cassata-d41682.netlify.app
claude mcp add --transport http lionmaster20-lion-mcp 'https://gleaming-cassata-d41682.netlify.app/api/mcp'
{
"mcpServers": {
"lionmaster20-lion-mcp": {
"url": "https://gleaming-cassata-d41682.netlify.app/api/mcp"
}
}
} {
"servers": {
"lionmaster20-lion-mcp": {
"type": "http",
"url": "https://gleaming-cassata-d41682.netlify.app/api/mcp"
}
}
} [mcp_servers.lionmaster20-lion-mcp] url = "https://gleaming-cassata-d41682.netlify.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lionmaster20-lion-mcp": {
"type": "remote",
"url": "https://gleaming-cassata-d41682.netlify.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add lionmaster20-lion-mcp --url 'https://gleaming-cassata-d41682.netlify.app/api/mcp' --transport streamable-http
mcp_servers:
lionmaster20-lion-mcp:
url: "https://gleaming-cassata-d41682.netlify.app/api/mcp" {
"McpServers": {
"lionmaster20-lion-mcp": {
"Transport": "http",
"Url": "https://gleaming-cassata-d41682.netlify.app/api/mcp"
}
}
} assistant mcp add lionmaster20-lion-mcp -t streamable-http -u 'https://gleaming-cassata-d41682.netlify.app/api/mcp'
{
"mcpServers": {
"lionmaster20-lion-mcp": {
"type": "http",
"url": "https://gleaming-cassata-d41682.netlify.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://gleaming-cassata-d41682.netlify.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gleaming-cassata-d41682.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gleaming-cassata-d41682.netlify.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://gleaming-cassata-d41682.netlify.app/api/mcp | HTTPS enforced | 301 | https://gleaming-cassata-d41682.netlify.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lion_adaptive_data_query ~420
LION Adaptive Data Fabric: ONE typed x402 query endpoint that adapts to any agent request over live Base on-chain data, covering multiple verticals from one call. Query params: source (base_dex | token_risk | defi_yields), token (0x address; for token_risk / single-token base_dex), sort (activity|volume|liquidity|age), limit, min_liquidity, max_age_hours, fields (output projection), q (free-text intent). base_dex = ranked active Base tokens (liquidity, volume, price-change, pair-age, activity_score) via DexScreener; token_risk = token security card (honeypot, buy/sell tax, mintable, owner, holders + mechanical risk_flags) via GoPlus; defi_yields = Base DeFi pools ranked by TVL with APY via DefiLlama. Free self-describing capability manifest at the same URL with ?describe=1 (no payment). Returns typed JSON rows + freshness fields (as_of, data_age_seconds, confidence, source_provider). Public keyless data, no API key. Raw public market data only - not financial or investment advice. Pay 0.005 USDC on Base via x402; tools/call returns payment-required metadata only, settle at the paid route to fetch the live JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated output field projection. |
| limit | integer | – | Max rows. |
| max_age_hours | number | – | Filter: max pair age in hours (base_dex). |
| min_liquidity | number | – | Filter: minimum liquidity/TVL in USD. |
| q | string | – | Free-text intent (echoed; reserved for semantic routing). |
| sort | string | – | Ranking key. |
| source | string | – | Which live data vertical to query. Default base_dex. |
| token | string | – | Base token address; required for token_risk, optional for base_dex single-token lookup. |
No output schema declared.
No examples provided.
lion_base_dex_signals_json ~164
Live Base (eip155:8453) DEX market-data feed for trading and research agents. Returns a fresh ranked snapshot of active Base tokens with raw on-chain metrics: price_usd, liquidity_usd, volume_h24, volume_m5, price_change_h1/h24, pair_age_hours, dex, and a transparent mechanical activity_score (volume + liquidity + recency). Source: public DexScreener data, no API key. Raw public market data only - not financial or investment advice, no buy/sell recommendation. Pay 0.005 USDC on Base via x402 at the paid route. tools/call returns payment-required metadata only; settle the x402 invoice at the paid route to fetch the live JSON.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lion_payment_attempt_readiness_audit ~226
Pre-spend payment-term trust check for x402 endpoints. Before your agent signs a Payment-Signature, call this with a target x402/MCP service URL: LION extracts the target live 402 payment terms (payTo, amount, asset, network, scheme), cross-checks them for drift across public discovery surfaces, and returns payment_attempt_blockers, buyer_policy_fit, canonical_purchase_recipe, funnel_stage, a transparent readiness score, and risk_flags so the agent can decide whether to sign. 0.05 USDC on Base eip155:8453. Unpaid tools/call returns JSON-RPC error -32402 with the x402 paymentRequirement; wallet-capable MCP clients (e.g. Coinbase Payments MCP, AWS AgentCore Payments) auto-construct the EIP-3009 signature. LION does NOT perform payment inside MCP. Checks payment-term consistency only - not a smart-contract security audit, no settlement guarantee, no fund movement.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public HTTPS x402/MCP service URL to audit. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| asset | string | yes | – |
| external_paid_proof | boolean | yes | – |
| instructions | string | yes | – |
| network | string | yes | – |
| paid_endpoint_url | string | yes | – |
| payTo | string | yes | – |
| price_usdc | string | yes | – |
| scheme | string | yes | – |
| status | string | yes | – |
No examples provided.
lion_trend_intent_signal_csv ~127
Hardware-wallet buyer-intent + self-custody onboarding-friction intelligence as flat CSV. Same column set as the JSON variant: Ledger vs Trezor comparison demand, Bitcoin-only wallet research, under-$100 wallet shopper queries, DeFi hardware-wallet intent, decision-stage crypto purchase research. Optimised for spreadsheet / pipeline ingestion and affiliate-routing or comparison-research workflows. Pay $0.01 USDC on Base mainnet via x402 at the paid route. tools/call returns payment-required metadata only; settle the invoice at the paid route to fetch the CSV.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lion_trend_intent_signal_json ~153
Hardware-wallet buyer-intent + self-custody onboarding-friction intelligence as JSON. Non-PII public-signal feed covering: Ledger vs Trezor comparison demand, Bitcoin-only wallet research, under-$100 wallet shopper queries, DeFi hardware-wallet intent, and adjacent decision-stage crypto purchase research. Designed for agent routing, affiliate / comparison-content workflows, and research context. Pay $0.01 USDC on Base mainnet via x402 (HTTP 402 + EIP-3009 transferWithAuthorization) at the paid route. This MCP tool does NOT return the dataset; tools/call returns payment-required metadata so an x402-capable client can settle and fetch the JSON directly.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the LION Trend Intent MCP server?
LION Trend Intent MCP is listed in the public MCP registry as io.github.LIONMASTER20/lion-mcp. Read-only x402-paid trend-intent MCP tools for JSON and CSV signals. This page covers its hosted endpoint (https://gleaming-cassata-d41682.netlify.app/api/mcp).
Is the LION Trend Intent MCP server safe to use?
LION Trend Intent MCP scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LION Trend Intent MCP server expose?
LION Trend Intent MCP exposes 5 tools: lion_trend_intent_signal_json, lion_trend_intent_signal_csv, lion_base_dex_signals_json, lion_adaptive_data_query, lion_payment_attempt_readiness_audit. Their descriptions and schemas cost roughly 1,090 tokens of context every time the server is loaded.
Does the LION Trend Intent MCP server require authentication?
No. We connected to LION Trend Intent MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LION Trend Intent MCP server still maintained?
LION Trend Intent MCP is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.