Remote MCP · Endpoint

Local Trades Kit MCP server

No. Local Trades Kit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.modernmustardseed.com/trades-kit

The last check completed an MCP handshake.

Registry name
com.modernmustardseed/trades-kit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
US data for home-service trades: service-area ZIPs, seasonal demand, review timing, service pages.
Listing
From the official MCP registry (active).
Recent checks of Local Trades Kit
CheckedResultHandshake
1 hour agoHandshake completed55 ms
1 day agoHandshake completed247 ms
2 days agoHandshake completed219 ms
3 days agoHandshake completed57 ms
4 days agoHandshake completed45 ms
5 days agoHandshake completed271 ms
6 days agoHandshake completed198 ms
9 days agoHandshake completed21 ms
11 days agoHandshake completed112 ms
14 days agoHandshake completed140 ms
16 days agoHandshake completed166 ms
18 days agoHandshake completed153 ms
20 days agoHandshake completed49 ms
22 days agoHandshake completed130 ms
24 days agoHandshake completed55 ms

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

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