Remote MCP · Endpoint

FinBridge MCP server

No. FinBridge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.gronox.kr/mcp

The last check completed an MCP handshake.

Registry name
kr.gronox/finbridge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
843 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Korean company disclosures in English: DART filings, financial statements, segments, 13F.
Listing
From the official MCP registry (active).
Recent checks of FinBridge
CheckedResultHandshake
1 hour agoHandshake completed843 ms
2 days agoHandshake completed668 ms
4 days agoHandshake completed688 ms
5 days agoHandshake completed946 ms
7 days agoHandshake completed883 ms
8 days agoHandshake completed693 ms
9 days agoHandshake completed936 ms
12 days agoHandshake completed859 ms
13 days agoHandshake completed660 ms
15 days agoHandshake completed692 ms
17 days agoHandshake completed628 ms
18 days agoHandshake completed656 ms
19 days agoHandshake completed1.09 s
20 days agoHandshake completed691 ms
21 days agoHandshake completed626 ms
21 days agoHandshake completed678 ms
23 days agoHandshake completed648 ms

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

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