Remote MCP · Endpoint

Answering Service Care MCP server

No. Answering Service Care answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://answeringservicecare.com/mcp

The last check completed an MCP handshake.

Registry name
com.answeringservicecare/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
57 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read-only facts about Answering Service Care: company info, services, pricing, site search.
Listing
From the official MCP registry (active).
Recent checks of Answering Service Care
CheckedResultHandshake
1 hour agoHandshake completed57 ms
2 days agoHandshake completed156 ms
4 days agoHandshake completed47 ms
6 days agoHandshake completed188 ms
8 days agoHandshake completed64 ms
10 days agoHandshake completed353 ms
12 days agoHandshake completed591 ms
13 days agoHandshake completed214 ms
14 days agoHandshake completed190 ms
15 days agoHandshake completed180 ms
18 days agoHandshake completed162 ms
20 days agoHandshake completed42 ms
21 days agoHandshake completed255 ms
23 days agoHandshake completed162 ms
24 days agoHandshake completed195 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 Answering Service Care and makes no claim about it beyond what these checks measured.