Remote MCP · Endpoint

A.U.G.U.R Foresight · Bundle Forensics MCP server

No. A.U.G.U.R Foresight · Bundle Forensics answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.augur-trade/foresight-forensics
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
4 tools
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
Who is behind a launch: bundles, insiders, airdrops, serial devs. Solana pump.fun + 18 EVM chains.
Listing
From the official MCP registry (active).
Recent checks of A.U.G.U.R Foresight · Bundle Forensics
CheckedResultHandshake
1 day agoHandshake completed122 ms
4 days agoHandshake completed67 ms
14 days agoHandshake completed31 ms
15 days agoHandshake completed100 ms
16 days agoFailed - the request timed out—
17 days agoFailed - the request timed out—
19 days agoHandshake completed96 ms
19 days agoHandshake completed107 ms
20 days agoHandshake completed96 ms
22 days agoHandshake completed94 ms
24 days agoHandshake completed29 ms
26 days agoHandshake completed35 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 · Bundle Forensics and makes no claim about it beyond what these checks measured.