Remote MCP · Endpoint

dev.answerline/answerline MCP server

No. dev.answerline/answerline answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://mcp.answerline.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.answerline/answerline
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
291 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
What ChatGPT, Gemini and Google answer — structured JSON with cited sources.
Listing
From the official MCP registry (active).
Recent checks of dev.answerline/answerline
CheckedResultHandshake
33 minutes agoHandshake completed291 ms
8 days agoHandshake completed293 ms
9 days agoHandshake completed296 ms
11 days agoHandshake completed292 ms
12 days agoHandshake completed296 ms
12 days agoHandshake completed291 ms
14 days agoHandshake completed297 ms
14 days agoHandshake completed296 ms
16 days agoHandshake completed289 ms
19 days agoHandshake completed292 ms
21 days agoHandshake completed413 ms
24 days agoHandshake completed298 ms
26 days agoHandshake completed313 ms
28 days agoHandshake completed291 ms

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

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