Remote MCP · Endpoint

FinzData market data MCP server

No. FinzData market data answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://api.finzdata.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.FinzData/finzdata-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
753 ms
Tools exposed
41 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
US stocks incl. delisted, futures, CPI/macro vintages, point-in-time GEX, 13F, COT, backtests.
Listing
From the official MCP registry (active).
Recent checks of FinzData market data
CheckedResultHandshake
19 minutes agoHandshake completed753 ms
9 days agoHandshake completed243 ms
9 days agoHandshake completed126 ms
11 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed94 ms
13 days agoHandshake completed98 ms
14 days agoHandshake completed102 ms
14 days agoHandshake completed556 ms
16 days agoHandshake completed212 ms
19 days agoHandshake completed365 ms
21 days agoHandshake completed158 ms
24 days agoHandshake completed178 ms
26 days agoHandshake completed237 ms
28 days agoHandshake completed203 ms

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

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