Remote MCP · Endpoint

FinChiefs research MCP server

No. FinChiefs research answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://finchiefs.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.finchiefs/research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.43 s
Tools exposed
16 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Research views, Daily Digest and Investment Themes from 200+ sources, plus official rates and data.
Website
https://finchiefs.com/mcp
Listing
From the official MCP registry (active).
Recent checks of FinChiefs research
CheckedResultHandshake
15 minutes agoHandshake completed1.43 s
9 days agoHandshake completed937 ms
9 days agoHandshake completed660 ms
11 days agoHandshake completed794 ms
12 days agoHandshake completed709 ms
13 days agoHandshake completed637 ms
14 days agoHandshake completed1.33 s
14 days agoHandshake completed572 ms
16 days agoHandshake completed730 ms
19 days agoHandshake completed821 ms
21 days agoHandshake completed657 ms
24 days agoCredentials required—

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with FinChiefs research and makes no claim about it beyond what these checks measured.