Remote MCP · Endpoint

dev.answerline/answerline MCP server

No. dev.answerline/answerline answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
313 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed313 ms
1 day agoHandshake completed291 ms
4 days agoHandshake completed289 ms
6 days agoHandshake completed292 ms
8 days agoHandshake completed289 ms
9 days agoHandshake completed303 ms
11 days agoHandshake completed314 ms
12 days agoHandshake completed295 ms
13 days agoHandshake completed294 ms
16 days agoHandshake completed290 ms
17 days agoHandshake completed288 ms
19 days agoHandshake completed308 ms
20 days agoHandshake completed289 ms
21 days agoCredentials required—
22 days agoCredentials required—

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