Remote MCP · Endpoint

Foresee MCP server

No. Foresee answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://agents.go-foresee.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Foresee-Tech/foresee
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
147 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Let AI assistants shop for home and auto insurance: compare quote estimates across every carrier.
Listing
From the official MCP registry (active).
Recent checks of Foresee
CheckedResultHandshake
52 minutes agoHandshake completed147 ms
2 days agoHandshake completed78 ms
4 days agoHandshake completed90 ms
5 days agoHandshake completed71 ms
7 days agoHandshake completed85 ms
8 days agoHandshake completed77 ms
9 days agoHandshake completed850 ms
11 days agoHandshake completed91 ms
13 days agoHandshake completed152 ms
15 days agoHandshake completed70 ms
17 days agoHandshake completed83 ms
18 days agoHandshake completed81 ms
19 days agoHandshake completed72 ms
20 days agoHandshake completed90 ms
21 days agoHandshake completed75 ms
21 days agoHandshake completed76 ms

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

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