Remote MCP · Endpoint

A.U.G.U.R Foresight MCP server

No. A.U.G.U.R Foresight answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.augur-trade/foresight
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
75 ms
Tools exposed
15 tools
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
Solana + pump.fun intel for agents: launch verdicts, token risk, dev/wallet records, smart money.
Listing
From the official MCP registry (active).
Recent checks of A.U.G.U.R Foresight
CheckedResultHandshake
30 minutes agoHandshake completed75 ms
3 days agoHandshake completed73 ms
13 days agoHandshake completed48 ms
14 days agoHandshake completed42 ms
15 days agoFailed - the request timed out—
16 days agoFailed - the request timed out—
17 days agoHandshake completed109 ms
18 days agoHandshake completed114 ms
19 days agoHandshake completed121 ms
21 days agoHandshake completed421 ms
23 days agoHandshake completed106 ms
25 days agoHandshake completed96 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 and makes no claim about it beyond what these checks measured.