Is ink.foresea/forecasting up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://foresea.ink/mcp/ |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://foresea.ink/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://foresea.ink with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 28 tools: foresea_analyze_market, foresea_batch_forecast, foresea_batch_quotes, foresea_cancel_order, foresea_check_run, foresea_crypto_edge, foresea_debate_market, foresea_edge_board, foresea_exchange_status, foresea_feed_latest, foresea_forecast, foresea_live_data, foresea_market_leaderboard, foresea_market_tags, foresea_optimize_portfolio, foresea_orderbook, foresea_place_order, foresea_polymarket_meta, foresea_preview_order, foresea_price_history, foresea_recent_trades, foresea_scan_markets, foresea_track_record, foresea_trade_account_status, foresea_venue_data, foresea_weather_forecast, foresea_weather_radar, foresea_webhook_subscribe.
Its tools changed between 2026-09 and 2026-10:
- Added (7):
foresea_batch_forecast,foresea_cancel_order,foresea_crypto_edge,foresea_place_order,foresea_preview_order,foresea_trade_account_status,foresea_webhook_subscribe foresea_edge_board: description, input schema changedforesea_track_record: description, input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | ink.foresea/forecasting |
|---|---|
| Endpoint | https://foresea.ink/mcp/ |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt