x402-paid MCP data: trend feed + visibility audit. USDC/Base. No API key. No PII.
Otherv1.1.1streamable-httpgleaming-cassata-d41682.netlify.app
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1442ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-03-26, serverInfo lion-trend-intent-mcp@0.4.0 |
| tooling | 35 / 35 | tools/list OK: 5 tools e.g. "lion_trend_intent_signal_json"; 5/5 described, 5/5 fully-typed schemas, median description 659 chars |
| latency | 7 / 10 | initialize round-trip 1442ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.1.1; namespace app.netlify.gleaming-cassata-d41682 matches endpoint/repo |
Score 94/100 · latency 1442ms · 5 tools · auth: open
Claude Code:
claude mcp add --transport http lion-mcp https://gleaming-cassata-d41682.netlify.app/api/mcp?src=mcpregistry_domain_v1_1
Generic MCP client config:
{ "mcpServers": { "lion-mcp": { "type": "http", "url": "https://gleaming-cassata-d41682.netlify.app/api/mcp?src=mcpregistry_domain_v1_1" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/app.netlify.gleaming-cassata-d41682/lion-mcp · referral link https://mcpqueen.com/go/app.netlify.gleaming-cassata-d41682/lion-mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/app.netlify.gleaming-cassata-d41682/lion-mcp)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 19:03 | A | 94 | 1442ms |