Remote MCP · Endpoint

Finbolt MCP server

No. Finbolt answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://api.getfinbolt.com/mcp

The last check completed an MCP handshake.

Registry name
com.getfinbolt/finbolt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
201 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
SEC-filed company financials with filing citations, plus market data, for AI agents
Listing
From the official MCP registry (active).
Recent checks of Finbolt
CheckedResultHandshake
37 minutes agoHandshake completed201 ms
4 days agoHandshake completed154 ms
7 days agoHandshake completed269 ms
16 days agoHandshake completed170 ms
16 days agoHandshake completed258 ms
18 days agoHandshake completed148 ms
19 days agoHandshake completed164 ms
20 days agoHandshake completed145 ms
21 days agoHandshake completed142 ms
22 days agoHandshake completed159 ms
23 days agoHandshake completed158 ms
26 days agoHandshake completed275 ms

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

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