Remote MCP · Endpoint

A.U.G.U.R Foresight · Web & Research MCP server

No. A.U.G.U.R Foresight · Web & Research answered an MCP handshake 29 minutes ago.

UpLast checked 29 minutes ago

Server URL

https://augur-trade.com/foresight/mcp/web

The last check completed an MCP handshake.

Registry name
com.augur-trade/foresight-web
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
64 ms
Tools exposed
15 tools
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
Read the web (page text, DNS, WHOIS, TLS, uptime) + research (Wikipedia, arXiv, GitHub, packages).
Listing
From the official MCP registry (active).
Recent checks of A.U.G.U.R Foresight · Web & Research
CheckedResultHandshake
29 minutes agoHandshake completed64 ms
3 days agoHandshake completed37 ms
13 days agoHandshake completed41 ms
14 days agoHandshake completed48 ms
15 days agoFailed - the request timed out—
16 days agoFailed - the request timed out—
17 days agoHandshake completed45 ms
18 days agoHandshake completed47 ms
19 days agoHandshake completed33 ms
21 days agoHandshake completed45 ms
22 days agoHandshake completed30 ms
25 days agoHandshake completed39 ms

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

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 A.U.G.U.R Foresight · Web & Research and makes no claim about it beyond what these checks measured.