mcp-registry/ink.foresea/forecasting · v1.30.0
As of 2026-10-21 05:37 UTC, the Foresea Forecasting MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 2 minutes.
Forecast future events and scan prediction-market edges.
Claude Code
claude mcp add --transport http foresea-forecasting-mcp-server https://foresea.ink/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"foresea-forecasting-mcp-server": {
"type": "http",
"url": "https://foresea.ink/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
28 of 28 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
106 parameter(s) across 25 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 →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
In the last 30 days: 0 tool(s) removed and 2 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 25 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fink.foresea%2Fforecasting/fixes
{
"name": "foresea_analyze_market",
"description": "Call this when the user mentions a specific prediction market by URL, slug,\n or ticker — or asks whether a particular market is over/underpriced. Good\n triggers: \"Is this Polymarket fair?\", \"What's the edge on kalshi:XXXXX?\",\n \"Should I buy/sell this market?\", user pastes a Polymarket or Kalshi URL.\n Fetches the live price, gathers evidence, forecasts, computes model-vs-market\n edge, and returns a recommendation. Use foresea_forecast instead when there is\n ",
"inputSchema": {
"type": "object",
"title": "foresea_analyze_marketArguments",
"properties": {
"slug": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Slug",
"default": null
},
"skills": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"additionalProperties": {
"type": "string"
}
}
},
{
"type": "null"
}
],
"title": "Skills",
"default": null
},
"ticker": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Ticker",
"default": null
},
"variant": {
"type": "string",
"title": "Variant",
"default": "variant0_neutral_baseline"
},
"platform": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Platform",
"default": null
},
"question": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Question",
"default": null
},
"market_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Market Id",
"default": null
},
"tool_loop": {
"type": "boolean",
"title": "Tool Loop",
"default": false
},
"builtin_skills": {
"type": "boolean",
"title": "Builtin Skills",
"default": false
},
"evidence_top_k": {
"type": "integer",
"title": "Evidence Top K",
"default": 5
},
"max_tool_steps": {
"type": "integer",
"title": "Max Tool Steps",
"default": 5
},
"ground_in_record": {
"type": "boolean",
"title": "Ground In Record",
"default": false
},
"market_probability": {
"anyOf": [
{
"type": "number"
},
{
"type": "null"
}
],
"title": "Market Probability",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "foresea_cancel_order",
"description": "Cancel an active open order on Kalshi or Polymarket using its venue order ID.",
"inputSchema": {
"type": "object",
"title": "foresea_cancel_orderArguments",
"required": [
"order_id"
],
"properties": {
"ticker": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Ticker",
"default": null
},
"order_id": {
"type": "string",
"title": "Order Id"
},
"platform": {
"type": "string",
"title": "Platform",
"default": "kalshi"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "foresea_check_run",
"description": "Call this after foresea_analyze_market timed out or errored with a\n message naming a client_run_key -- the research it started may still be\n running server-side. Returns {\"status\": \"running\", ...} if it's not done\n yet (call again in a bit), or the full report once it is. Do not call\n this speculatively; only use the client_run_key a prior\n foresea_analyze_market call actually gave you.\n Example: client_run_key=\"a1b2c3...\" → {status:\"running\", id:\"agent_",
"inputSchema": {
"type": "object",
"title": "foresea_check_runArguments",
"required": [
"client_run_key"
],
"properties": {
"client_run_key": {
"type": "string",
"title": "Client Run Key"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/ink.foresea/forecasting"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ink.foresea/forecasting"}) over MCP.
foresea_forecast ~515 tokensforesea_analyze_market ~505 tokensforesea_place_order ~382 tokensforesea_preview_order ~295 tokensforesea_scan_markets ~277 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fink.foresea%2Fforecasting?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fink.foresea%2Fforecasting?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fink.foresea%2Fforecasting.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fink.foresea%2Fforecasting.svg :target: https://glimind.com/server/mcp-registry%2Fink.foresea%2Fforecasting?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7a247f739649e6aa…, first seen 2026-10-17, included at leaf 11 of 37,421. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable finance servers · most reliable other servers · most reliable knowledge servers · most reliable data servers
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.
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"
}
}
}
As of 2026-10-21 05:37 UTC, the Foresea Forecasting MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 2 minutes.
Foresea Forecasting MCP server advertises 28 tools, including foresea_analyze_market, foresea_batch_forecast, foresea_batch_quotes, foresea_cancel_order, foresea_check_run.
Point your MCP client at this streamable-http endpoint: https://foresea.ink/mcp/
Glimind scanned all 28 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.
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.