Remote MCP · Endpoint

AnsweringPrices.com pricing MCP server

No. AnsweringPrices.com pricing answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://www.answeringprices.com/mcp/

The last check completed an MCP handshake.

Registry name
com.answeringprices/pricing
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Dated answering service prices, plans, billing terms, and comparisons at your call volume.
Listing
From the official MCP registry (active).
Recent checks of AnsweringPrices.com pricing
CheckedResultHandshake
13 minutes agoHandshake completed111 ms
9 days agoHandshake completed80 ms
9 days agoHandshake completed78 ms
11 days agoHandshake completed121 ms
12 days agoHandshake completed129 ms
13 days agoHandshake completed574 ms
14 days agoHandshake completed274 ms
15 days agoHandshake completed467 ms
16 days agoHandshake completed171 ms
19 days agoHandshake completed139 ms
21 days agoHandshake completed911 ms
24 days agoHandshake completed125 ms
26 days agoHandshake completed111 ms
28 days agoHandshake completed776 ms

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

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