Remote MCP · Endpoint

TDE MCP server

No. TDE answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.tdehq.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.danha2048/tde
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
216 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Before you sign a trade deal: what it does to your cash month by month, and what to ask for instead.
Website
https://tdehq.com/
Listing
From the official MCP registry (active).
Recent checks of TDE
CheckedResultHandshake
1 hour agoHandshake completed216 ms
9 days agoHandshake completed200 ms
10 days agoHandshake completed221 ms
11 days agoHandshake completed157 ms
12 days agoHandshake completed162 ms
14 days agoHandshake completed184 ms
14 days agoHandshake completed182 ms
15 days agoHandshake completed184 ms
17 days agoHandshake completed366 ms
19 days agoHandshake completed231 ms
21 days agoHandshake completed168 ms
24 days agoHandshake completed417 ms
26 days agoHandshake completed178 ms

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

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