Is the Foresee Tech Foresee MCP server down?

mcp-registry/io.github.foresee-tech/foresee · v4.0.0

healthy
Last checked 2026-10-27 01:27 UTC · handshake 100ms

As of 2026-10-27 01:27 UTC, the Foresee Tech Foresee MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
5,007
outages (90d)
0
tools
2

Let AI assistants shop for home and auto insurance: compare instant quotes across every carrier.

Point your MCP client at this streamable-http endpoint: https://agents.go-foresee.com/mcp

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 2 warning(s) across 2 tool(s); ~13,548 tokens of tool definitions.
Scores higher than 11% of 15,772 MCP servers Glimind has audited.
Its tool list costs an agent ~13,548 tokens per session — more than 85% of servers.
75 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints100
Token cost50
Client compatibility100
Protocol100
Reliability100
Stability52

What to fix (3)

2 tool definition(s) exceed ~1,200 tokens each (largest: live_carrier_quotes, ~7,264).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~12,348 tokens every session. How to fix →

Tools: live_carrier_quotes, quote_insurance · saves ~12,348 tokens/session

8 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: live_carrier_quotes, quote_insurance

In the last 30 days: 0 tool(s) removed and 12 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.foresee-tech/foresee"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.foresee-tech/foresee"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.foresee-tech%2Fforesee.svg)](https://glimind.com/server/mcp-registry%2Fio.github.foresee-tech%2Fforesee?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.foresee-tech%2Fforesee?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.foresee-tech%2Fforesee.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.foresee-tech%2Fforesee.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.foresee-tech%2Fforesee?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:47c49b1b00c21623…, first seen 2026-10-17, included at leaf 2865 of 76,584. Version history · verify what your client received.

Tools (2)

Compare: most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Foresee Tech Foresee MCP server down right now?

As of 2026-10-27 01:27 UTC, the Foresee Tech Foresee MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Foresee Tech Foresee MCP server provide?

Foresee Tech Foresee MCP server advertises 2 tools, including live_carrier_quotes, quote_insurance.

How do I install Foresee Tech Foresee MCP server?

Point your MCP client at this streamable-http endpoint: https://agents.go-foresee.com/mcp

Is the Foresee Tech Foresee MCP server safe to connect to an AI agent?

Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Foresee Tech Foresee MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve