Remote MCP · Endpoint
Contractors Near Me MCP server
No. Contractors Near Me answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://contractorsnearme.ai/api/mcp
The last check completed an MCP handshake.
- Registry name
- ai.contractorsnearme/contractors-near-me
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 168 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 31.6% from 19 checks
- Described by its publisher as
- Search licensed US contractors by trade or location, fetch profiles and reviews, and submit leads.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 168 ms |
| 22 hours ago | Handshake completed | 135 ms |
| 2 days ago | Handshake completed | 61 ms |
| 3 days ago | Handshake completed | 88 ms |
| 4 days ago | Handshake completed | 68 ms |
| 5 days ago | Handshake completed | 86 ms |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Failed - the check failed for an unclassified reason | — |
| 11 days ago | Failed - the check failed for an unclassified reason | — |
| 13 days ago | Failed - the check failed for an unclassified reason | — |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 18 days ago | Failed - the check failed for an unclassified reason | — |
| 20 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 24 days ago | Failed - the check failed for an unclassified reason | — |
| 25 days ago | Failed - the check failed for an unclassified reason | — |
| 27 days ago | Failed - the check failed for an unclassified reason | — |
| 29 days ago | Failed - the check failed for an unclassified reason | — |
| 29 days ago | Failed - the check failed for an unclassified reason | — |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 30.
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 Near Me and makes no claim about it beyond what these checks measured.