Remote MCP · Endpoint

Tiingo MCP server

No. Tiingo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/tiingo/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/tiingo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Tiingo MCP — wraps the Tiingo financial API (tiingo.com)
Listing
From the official MCP registry (active).
Recent checks of Tiingo
CheckedResultHandshake
1 hour agoHandshake completed60 ms
2 days agoHandshake completed69 ms
4 days agoHandshake completed82 ms
6 days agoHandshake completed53 ms
7 days agoHandshake completed86 ms
8 days agoHandshake completed58 ms
9 days agoHandshake completed99 ms
12 days agoHandshake completed46 ms
14 days agoHandshake completed41 ms
15 days agoHandshake completed279 ms
17 days agoHandshake completed46 ms
18 days agoHandshake completed50 ms
19 days agoHandshake completed47 ms
20 days agoHandshake completed91 ms
21 days agoHandshake completed41 ms
22 days agoHandshake completed59 ms
23 days agoHandshake completed43 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 Tiingo and makes no claim about it beyond what these checks measured.