Remote MCP · Endpoint

Entervista MCP server

No. Entervista answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://entervista.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.entervista/entervista
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
43 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find and book local service businesses (plumbers, HVAC, detailers) at real prices, with approval.
Listing
From the official MCP registry (active).
Recent checks of Entervista
CheckedResultHandshake
44 minutes agoHandshake completed43 ms
8 days agoHandshake completed29 ms
9 days agoHandshake completed30 ms
11 days agoHandshake completed31 ms
12 days agoHandshake completed34 ms
13 days agoHandshake completed29 ms
14 days agoHandshake completed48 ms
14 days agoHandshake completed30 ms
16 days agoHandshake completed45 ms
19 days agoHandshake completed29 ms
21 days agoHandshake completed34 ms
24 days agoHandshake completed41 ms
26 days agoHandshake completed305 ms
28 days agoHandshake completed39 ms

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

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