Remote MCP · Endpoint

Tradify MCP Server and API by Cotlet MCP server

No. Tradify MCP Server and API by Cotlet answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://cotlet.dev/mcp/v1/tradify

The last check completed an MCP handshake.

Registry name
dev.cotlet/tradify
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
199 ms
Tools exposed
53 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Tradify job management for trades MCP server: create job, create quote, send invoice.
Listing
From the official MCP registry (active).
Recent checks of Tradify MCP Server and API by Cotlet
CheckedResultHandshake
42 minutes agoHandshake completed199 ms
3 days agoHandshake completed1.24 s
12 days agoHandshake completed300 ms
12 days agoHandshake completed182 ms
14 days agoHandshake completed149 ms
15 days agoHandshake completed162 ms
16 days agoHandshake completed155 ms
17 days agoHandshake completed241 ms
18 days agoHandshake completed173 ms
20 days agoHandshake completed357 ms
22 days agoHandshake completed156 ms
25 days agoHandshake completed179 ms

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.

Listing data comes from the official MCP registry. Glide is not affiliated with Tradify MCP Server and API by Cotlet and makes no claim about it beyond what these checks measured.