Remote MCP · Endpoint

ETFIQ MCP server

No. ETFIQ answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.etfiq.com/

The last check completed an MCP handshake.

Registry name
com.etfiq/etfiq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
33 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Independent US ETF data for research agents: flows, news, strategies, risk checks, each dated.
Listing
From the official MCP registry (active).
Recent checks of ETFIQ
CheckedResultHandshake
1 hour agoHandshake completed55 ms
1 day agoHandshake completed62 ms
2 days agoHandshake completed75 ms
3 days agoHandshake completed163 ms
4 days agoHandshake completed126 ms
5 days agoHandshake completed83 ms
7 days agoHandshake completed357 ms
10 days agoHandshake completed56 ms
12 days agoHandshake completed121 ms
14 days agoHandshake completed53 ms
17 days agoHandshake completed68 ms
19 days agoHandshake completed53 ms
21 days agoHandshake completed67 ms
23 days agoHandshake completed80 ms
25 days agoHandshake completed72 ms
26 days agoHandshake completed47 ms
28 days agoHandshake completed76 ms
29 days agoHandshake completed285 ms

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

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