General Tools
go-foresee.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://agents.go-foresee.com/mcp
MCP server metadata
- Name
- foresee
- Version
- 1.27.2
Foresee quotes auto in CA today. Get personal lines insurance quote estimates. Start with quote_insurance. `lines` is REQUIRED — ONE map from line name in plain words (auto, renters, home…) to that line's coverage ask as actual numbers. Best results: quote in your FIRST reply — when coverage wasn't chosen, price the common starting point (bi "100/300", pd 100, coll_deductible 500, comp_deductible 500) as an adjustable, declared assumption rather than asking first. State only numbers the result contains — never interpolate. A renters ask names coverage_c (contents limit), coverage_e (liability), coverage_f (guest medical) and deductible; a home ask names coverage_a (dwelling limit, at replacement cost), coverage_e, coverage_f and aop_deductible — all in dollars. A line that isn't live yet comes back under skipped with honest copy — relay it, never quote a different line instead. ZIP, age and (for auto) the vehicle's year/make/model are REQUIRED with no server fallback: when the user implied one ('Sacramento', 'mid-20s'), pass a concrete value and tell them the assumption. Other omitted profile fields come back as explicit declared assumptions to relay, so you'll rarely need follow-up questions before the first call; only when most of the required facts are missing, ask ONE short round of 2-4 (plus military_affiliation when it might apply — USAA quotes only military members, veterans, and their families), then call with everything known — the response's assumptions, profile_required and coverage_required name anything still open, so a second round of questions never beats a first quote. After presenting quotes, offer to refine: each line's tighten_by list names the missing facts that most move the price — ask the user for them and re-quote with the answers — and each carrier's price_ladder answers limit/deductible what-ifs with exact one-lever prices (deductibles follow the user's cash buffer, liability limits their assets); a combined change is a re-call with the new ask. live_carrier_quotes submits profile details to the carriers' own websites — the user's own details or a hypothetical/synthetic profile both work; explicit user authorization required. The call is idempotent per profile + coverage selection: call it again with the same arguments to collect progress and results — a profile already walked returns those results without re-submitting to the carriers.
Known tools 2
quote_insurancePurpose: 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.
Inferred read-onlylive_carrier_quotesPurpose: confirm quote estimates on the carriers' own quote sites, via Foresee agents completing their real quote flows.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.foresee]
url = "https://agents.go-foresee.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"foresee": {
"type": "http",
"url": "https://agents.go-foresee.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: foresee
Remote MCP URL: https://agents.go-foresee.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"foresee": {
"url": "https://agents.go-foresee.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"foresee": {
"type": "http",
"url": "https://agents.go-foresee.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "foresee",
"transport": "streamable-http",
"url": "https://agents.go-foresee.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.