Remote MCP · Endpoint

Twelvedata MCP server

No. Twelvedata answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/twelvedata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
88 ms
Tools exposed
61 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Twelve Data MCP.
Listing
From the official MCP registry (active).
Recent checks of Twelvedata
CheckedResultHandshake
1 hour agoHandshake completed88 ms
19 hours agoHandshake completed128 ms
2 days agoHandshake completed116 ms
3 days agoHandshake completed150 ms
4 days agoHandshake completed61 ms
5 days agoHandshake completed115 ms
6 days agoHandshake completed118 ms
8 days agoHandshake completed145 ms
11 days agoHandshake completed66 ms
13 days agoHandshake completed93 ms
15 days agoHandshake completed157 ms
18 days agoHandshake completed70 ms
20 days agoHandshake completed57 ms
22 days agoHandshake completed69 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed53 ms
27 days agoHandshake completed58 ms
29 days agoHandshake completed66 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 Twelvedata and makes no claim about it beyond what these checks measured.