Remote MCP · Endpoint

Agent Net Answers MCP server

No. Agent Net Answers answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://104.131.179.1/mcp

The last check completed an MCP handshake.

Registry name
io.github.ebspark/agent-net-answers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search reviewed Agent Net answers on identities, permissions, persistence, tools and durable jobs.
Listing
From the official MCP registry (active).
Recent checks of Agent Net Answers
CheckedResultHandshake
2 hours agoHandshake completed49 ms
1 day agoHandshake completed38 ms
3 days agoHandshake completed38 ms
3 days agoHandshake completed43 ms
4 days agoHandshake completed42 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed42 ms
10 days agoHandshake completed42 ms
12 days agoHandshake completed44 ms
15 days agoHandshake completed63 ms
17 days agoHandshake completed43 ms
19 days agoHandshake completed38 ms
21 days agoHandshake completed42 ms
23 days agoHandshake completed37 ms
25 days agoHandshake completed36 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 Agent Net Answers and makes no claim about it beyond what these checks measured.