Remote MCP · Endpoint
熔岩 Lava · A股机构/大V消息面热度监测 MCP server
No — it is up, but it requires credentials. 熔岩 Lava · A股机构/大V消息面热度监测 answered 58 minutes ago with an authentication challenge rather than a session.
Auth requiredLast checked 58 minutes ago
Server URL
https://lava.ai-dolphin.com/subscribe/v1/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- io.github.dustinliang666-blip/lava-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- 查A股个股/概念最近被多少机构/大V提及、热度高不高。只读数据，机构/大V用匿名ID。量化交易必备。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 58 minutes ago | Credentials required | — |
| 11 hours ago | Credentials required | — |
| 2 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with 熔岩 Lava · A股机构/大V消息面热度监测 and makes no claim about it beyond what these checks measured.