Remote MCP · Endpoint

VettedHome property guides MCP server

No. VettedHome property guides answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vettedhome.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.vettedhome/property-guides
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
279 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search VettedHome's UK guides to property problems and home energy decisions. Read-only.
Listing
From the official MCP registry (active).
Recent checks of VettedHome property guides
CheckedResultHandshake
1 hour agoHandshake completed279 ms
3 days agoHandshake completed157 ms
12 days agoHandshake completed185 ms
12 days agoHandshake completed167 ms
14 days agoHandshake completed134 ms
15 days agoHandshake completed160 ms
16 days agoHandshake completed206 ms
17 days agoHandshake completed139 ms
18 days agoHandshake completed153 ms
19 days agoHandshake completed168 ms
22 days agoHandshake completed119 ms
25 days agoHandshake completed187 ms
27 days agoHandshake completed725 ms

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

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 VettedHome property guides and makes no claim about it beyond what these checks measured.