Remote MCP · Endpoint

Trades With AI + SaaS Price Watch MCP server

No. Trades With AI + SaaS Price Watch answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://tradeswithai.com/mcp

The last check completed an MCP handshake.

Registry name
com.tradeswithai/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only data: AI tools for trades businesses and public SaaS pricing, with source quotes.
Listing
From the official MCP registry (active).
Recent checks of Trades With AI + SaaS Price Watch
CheckedResultHandshake
3 hours agoHandshake completed122 ms
9 days agoHandshake completed119 ms
10 days agoHandshake completed294 ms
11 days agoHandshake completed134 ms
12 days agoHandshake completed163 ms
14 days agoHandshake completed161 ms
14 days agoHandshake completed122 ms
15 days agoHandshake completed109 ms
17 days agoHandshake completed354 ms
19 days agoHandshake completed171 ms
21 days agoHandshake completed136 ms
24 days agoHandshake completed123 ms
26 days agoHandshake completed141 ms
28 days agoHandshake completed98 ms

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

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 Trades With AI + SaaS Price Watch and makes no claim about it beyond what these checks measured.