Remote MCP · Endpoint

TokenBel Financial Data MCP server

No. TokenBel Financial Data answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
230 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 14 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
6 hours agoHandshake completed230 ms
9 days agoHandshake completed350 ms
10 days agoHandshake completed326 ms
11 days agoHandshake completed307 ms
12 days agoHandshake completed273 ms
14 days agoHandshake completed281 ms
15 days agoHandshake completed652 ms
15 days agoHandshake completed266 ms
17 days agoHandshake completed306 ms
19 days agoHandshake completed389 ms
22 days agoHandshake completed418 ms
24 days agoHandshake completed259 ms
26 days agoHandshake completed321 ms
28 days agoHandshake completed332 ms

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

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.