# Foresee (remote · agents.go-foresee.com)

Let AI assistants shop for home and auto insurance: compare quote estimates across every carrier.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agents.go-foresee.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/foresee-tech-foresee/agents.md), [page](https://verifymcp.io/servers/foresee-tech-foresee/agents)

## Channel facts

- Endpoint: `https://agents.go-foresee.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `4.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (live_carrier_quotes).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 53/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4776 tokens (~2388/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 20% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Foresee MCP server?

Foresee is a hosted endpoint at https://agents.go-foresee.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http foresee-tech-foresee 'https://agents.go-foresee.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "foresee-tech-foresee": {
      "url": "https://agents.go-foresee.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "foresee-tech-foresee": {
      "type": "http",
      "url": "https://agents.go-foresee.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.foresee-tech-foresee]
url = "https://agents.go-foresee.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "foresee-tech-foresee": {
      "type": "remote",
      "url": "https://agents.go-foresee.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add foresee-tech-foresee --url 'https://agents.go-foresee.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  foresee-tech-foresee:
    url: "https://agents.go-foresee.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "foresee-tech-foresee": {
      "Transport": "http",
      "Url": "https://agents.go-foresee.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add foresee-tech-foresee -t streamable-http -u 'https://agents.go-foresee.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "foresee-tech-foresee": {
      "type": "http",
      "url": "https://agents.go-foresee.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73, +1)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 72, −1)

- [functional] Stability: pass → 0.97

### 2026-11-01 (score 73, +4)

- [security improvement] Stability: fail → pass

### 2026-10-23 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 68 to 72.

### 2026-10-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 62 to 65.

### 2026-10-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 55 to 58.

### 2026-10-17 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 48 to 52.

### 2026-10-15 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 42 to 45.

## MCP tools (2)

### `quote_insurance` (~2245 tokens)

Instant insurance quote estimates

Purpose: generate instant, itemized quote estimates from the carriers
    Foresee supports, across the lines and states Foresee currently serves,
    in one call — the LIVE TODAY line at the end of this description names
    today's set.

    `lines` is REQUIRED and is ONE map: each key names a line to price (e.g.
    "auto", "renters", "home" — plain words are fine), each value is that
    line's coverage ask as actual numbers. A line Foresee doesn't quote in
    the user's state comes back under `skipped`: `lines` names each one and
    `message` is one sentence, written to be relayed to the user as-is,
    naming what Foresee does quote in that state. For auto
    the ask has four axes — `bi` (bodily-injury liability, per-person/
    per-accident in $000s, e.g. "100/300"), `pd` (property-damage liability in
    $000s, e.g. 100), `coll_deductible` (collision deductible in dollars, e.g.
    500) and `comp_deductible` (comprehensive deductible in dollars, e.g.
    500); `um` and `medpay` are optional. A renters ask has four axes —
    `coverage_c` (personal-property/contents limit in dollars, e.g. 30000),
    `coverage_e` (personal liability in dollars, e.g. 100000), `coverage_f`
    (guest medical in dollars, e.g. 1000) and `deductible` (all-perils, in
    dollars, e.g. 500); `coverage_d` is optional. A home ask: `coverage_a`
    (the dwelling's replacement cost in dollars), `coverage_e` (e.g. 300000),
    `coverage_f` (e.g. 1000) and `aop_deductible` (all-other-perils
    deductible in dollars, e.g. 1000). There are no named coverage levels
    and the server never defaults: pass exact numbers. An omitted OPTIONAL
    axis (`um`, `medpay`, `coverage_d`) keeps each carrier's own
    default — the quote's per-coverage lines show what was rated. Any
    numbers at or above the state's legal minimum work as the ask (an auto
    `bi`/`pd` below it prices nothing — no carrier may sell that policy — and
    comes back under `coverage_required` naming the minimum); each…

Input parameters:

- `carriers`: Price only these carriers, named by the `carrier_key` results carry (e.g. ["geico", "statefarm"]). Omit to price every carrier Foresee supports; a named carrier Foresee can't price comes back in `fai…
- `include_failures` (boolean): Report each carrier Foresee couldn't price under `failures`, with the reason. Leave true unless the user asked to see priced carriers only.
- `lines` (object, required)
- `profile` (object, required)

Output parameters:

- `bundle`
- `by_line`
- `coverage_required`
- `dense`
- `detail`
- `error`
- `example_arguments`
- `message`
- `presentation`
- `profile_required`
- `serviceable`
- `skipped`
- `state`

### `live_carrier_quotes` (~1995 tokens)

Live carrier quotes

Purpose: confirm quote estimates on the carriers' own quote sites, via Foresee agents completing their real quote flows.

        IDEMPOTENT, keyed on the profile: the first call commissions the
        walks; calling again with the same profile collects progress and
        results instead of re-submitting anything — whatever the ask. A
        profile that has already been walked returns those results (the
        carriers are never asked twice): the envelope's
        ``coverage_selection`` names the ask the walk typed, and each quote
        carries the carrier's other recorded coverage options as
        ``variants``, so a new ask reads the same run. So call once to
        start, then re-call after a few minutes to collect; agents still
        working report their stage.

        Ask ONCE, before the first call: the consent disclosure below, the
        identity fields, and the questions listed at the end of this
        description under EVERY LINE and under the line being walked — all
        in one message, so the first commissioning call walks every carrier. A call made before
        consent submits nothing and answers ``authorization_required`` with
        the profile's ``needs``, for when you have not asked yet.

        No sign-in is required. The one hard requirement is the user's own
        consent, captured in-band: BEFORE the commissioning call, you MUST
        tell the user, plainly: Foresee will submit their details to the
        named carriers; the carriers may obtain their credit-based insurance
        score (a soft pull, with no impact on your credit score); and the
        carriers may contact them by email or phone. Then get their explicit
        go-ahead and pass their affirmation VERBATIM as ``user_authorization``
        (e.g. "yes, go ahead"). The affirmation is stored as the durable
        consent record for the dispatch; without one the call is refused with
        ``authorization_required``. Foresee only collects quotes; it d…

Input parameters:

- `carriers`
- `dispatch_ready_only` (boolean)
- `identity`
- `lines`
- `profile` (object, required)
- `user_authorization` (string)

Output parameters:

- `agents`
- `assumptions`
- `authorization_recorded`
- `coverage_selection`
- `detail`
- `error`
- `example_arguments`
- `needs`
- `note`
- `ready`
- `recover`
- `skipped`
- `status`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/foresee-tech-foresee/agents#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 69
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 67
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 63
- 2026-10-10: 62
- 2026-10-06: 61
- 2026-10-04: 49
- 2026-10-03: 49
- 2026-10-02: 59

## Common questions

### What is the Foresee MCP server?

Foresee is an MCP server listed in the public MCP registry as io.github.Foresee-Tech/foresee. Let AI assistants shop for home and auto insurance: compare quote estimates across every carrier. This page covers its hosted endpoint (https://agents.go-foresee.com/mcp).

### Is the Foresee MCP server safe to use?

Foresee scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Foresee MCP server expose?

Foresee exposes 2 tools: quote_insurance, live_carrier_quotes. Their descriptions and schemas cost roughly 4,240 tokens of context every time the server is loaded.

### Does the Foresee MCP server require authentication?

No. We connected to Foresee without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Foresee MCP server still maintained?

Foresee is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Foresee MCP server?

VerifyMCP ran 13 checks on Foresee, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agents.go-foresee.com/mcp
- Repository: https://github.com/Foresee-Tech/foresee
- Website: https://go-foresee.com/
- Changelog RSS feed: https://verifymcp.io/servers/foresee-tech-foresee/agents.xml
- Changelog JSON feed: https://verifymcp.io/servers/foresee-tech-foresee/agents/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/foresee-tech-foresee/agents.json
- HTML version of this page: https://verifymcp.io/servers/foresee-tech-foresee/agents