Remote MCP · Endpoint

AnswerPool MCP server

No. AnswerPool answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://answerpool.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.blakeyounger/answerpool
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
292 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Computed SEC, Federal Register, federal funding and research-momentum signals
Listing
From the official MCP registry (active).
Recent checks of AnswerPool
CheckedResultHandshake
1 hour agoHandshake completed292 ms
2 days agoHandshake completed175 ms
4 days agoHandshake completed136 ms
5 days agoHandshake completed128 ms
7 days agoHandshake completed131 ms
8 days agoHandshake completed303 ms
9 days agoHandshake completed151 ms
12 days agoHandshake completed148 ms
13 days agoHandshake completed170 ms
15 days agoHandshake completed131 ms
16 days agoHandshake completed159 ms
18 days agoHandshake completed139 ms
19 days agoHandshake completed137 ms
20 days agoHandshake completed141 ms
20 days agoHandshake completed354 ms
21 days agoHandshake completed135 ms
22 days agoHandshake completed157 ms

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

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