Remote MCP · Endpoint
Dados B3 MCP server
No. Dados B3 answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://dadosb3.com/mcp/
The last check completed an MCP handshake.
- Registry name
- io.github.Val7h/dados-b3
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 258 ms
- Tools exposed
- 25 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Brazilian stock (B3) fundamentals: ratios, dividends, scores, FIIs, ETFs, BDRs. Open methodology.
- Repository
- https://github.com/Val7h/dados-b3-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 258 ms |
| 2 days ago | Handshake completed | 308 ms |
| 4 days ago | Handshake completed | 191 ms |
| 6 days ago | Handshake completed | 124 ms |
| 7 days ago | Handshake completed | 160 ms |
| 9 days ago | Handshake completed | 182 ms |
| 10 days ago | Handshake completed | 133 ms |
| 11 days ago | Handshake completed | 136 ms |
| 14 days ago | Handshake completed | 274 ms |
| 15 days ago | Handshake completed | 260 ms |
| 17 days ago | Handshake completed | 116 ms |
| 18 days ago | Handshake completed | 129 ms |
| 19 days ago | Handshake completed | 271 ms |
| 20 days ago | Handshake completed | 119 ms |
| 21 days ago | Handshake completed | 261 ms |
| 22 days ago | Handshake completed | 2.15 s |
| 23 days ago | Handshake completed | 104 ms |
| 24 days ago | Handshake completed | 194 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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 Dados B3 and makes no claim about it beyond what these checks measured.