Remote MCP · Endpoint

contractors.fyi MCP server

No. contractors.fyi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://contractors.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.contractors/contractors
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
354 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
US contractors ranked by city permits, permit costs and timelines, solar and generator sizing.
Listing
From the official MCP registry (active).
Recent checks of contractors.fyi
CheckedResultHandshake
1 hour agoHandshake completed354 ms
2 days agoHandshake completed393 ms
4 days agoHandshake completed533 ms
6 days agoHandshake completed405 ms
7 days agoHandshake completed324 ms
9 days agoHandshake completed360 ms
10 days agoHandshake completed404 ms
11 days agoHandshake completed485 ms
14 days agoHandshake completed230 ms
15 days agoHandshake completed209 ms
17 days agoHandshake completed353 ms
19 days agoHandshake completed258 ms
20 days agoHandshake completed191 ms
21 days agoHandshake completed236 ms
22 days agoHandshake completed346 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 contractors.fyi and makes no claim about it beyond what these checks measured.