Remote MCP · Endpoint

TokenBel Financial Data MCP server

No. TokenBel Financial Data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.tokenbel.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.AndreiDrang/tokenbel-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
332 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read-only MCP server for Belarusian securities: tokens, shares, bonds, companies.
Listing
From the official MCP registry (active).
Recent checks of TokenBel Financial Data
CheckedResultHandshake
1 hour agoHandshake completed332 ms
1 day agoHandshake completed378 ms
4 days agoHandshake completed344 ms
6 days agoHandshake completed432 ms
7 days agoHandshake completed233 ms
9 days agoHandshake completed487 ms
10 days agoHandshake completed828 ms
11 days agoHandshake completed209 ms
14 days agoHandshake completed284 ms
15 days agoHandshake completed249 ms
17 days agoHandshake completed273 ms
18 days agoHandshake completed424 ms
20 days agoHandshake completed269 ms
21 days agoHandshake completed272 ms
22 days agoHandshake completed329 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 TokenBel Financial Data and makes no claim about it beyond what these checks measured.