tools4foresight
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
MCP Tools4Foresight
Read-only MCP server for the foresight signals from tools4foresight.com. It gives an agent access to the same map a member sees: curated signals, the semantic graph, themes with their history, and the three horizons.
It writes nothing. There is not a single tool that modifies, publishes, or deletes
anything. See SECURITY.md.
What an agent can do with this
"What is the state of the map?" → H1/H2/H3 overview with its macro-themes.
"Which themes are growing and which are fading?" → time series per theme.
"Summarize the AI agents theme" → profile with its four indicators and its signals.
"What is similar to this signal?" → semantic neighbors, without leaving the curated map.
"What weak signals are there in H3?" → small themes with high novelty.
"What died this month?" → fossils, by comparing snapshots.
Related MCP server: Nostradamus Intellect
Installation
You need a tools4foresight API key (ask whoever administers it).
Claude Code
claude mcp add tools4foresight \
--env T4F_API_KEY=tu-api-key \
-- npx -y mcp-tools4foresightClaude Desktop
In claude_desktop_config.json:
{
"mcpServers": {
"tools4foresight": {
"command": "npx",
"args": ["-y", "mcp-tools4foresight"],
"env": { "T4F_API_KEY": "tu-api-key" }
}
}
}Cursor
In .cursor/mcp.json, the same block as Claude Desktop.
Remote (HTTP)
If you prefer to deploy it once and have several agents use it, see
docs/DEPLOYMENT.md. The remote endpoint requires its own
credential (MCP_ACCESS_TOKEN), different from the API key.
There is a complete example in .mcp.json.example.
Environment variables
Variable | Required | Default | What it is |
| yes | — | This server's key against the tools4foresight API |
| no |
| Useful for pointing to a local environment |
| no |
| Timeout per request |
| no |
| Retries on 429/5xx/network. A 401 is never retried |
| no |
|
|
| no |
|
|
| HTTP only | — | Credential this server requires from whoever calls it |
| no |
| Local HTTP server port |
The 18 tools
Full reference with examples in docs/TOOLS.md.
Topic | Tools |
Signals |
|
Themes |
|
Horizons |
|
Taxonomy |
|
Graph |
|
Snapshots |
|
Method |
|
Plus 7 resources, to attach context by hand from Claude Desktop or Cursor:
foresight://overview, ://glossary, ://horizons, ://signal/{id},
://theme/{id}, ://horizon/{key}, and ://macro-theme/{id}.
And 6 prompts —suggested conversation scripts, which give no extra
capability— for the questions that come up repeatedly: analizar_horizonte,
informe_de_tema, radar_semanal, senales_debiles, comparar_temas, and
explorar_desde_senal.
This server is for exploring: publishing, unpublishing, editing the analysis, or recomputing the graph are still done from tools4foresight, and none of that is exposed here.
Three things worth knowing before reading the output
A signal's date is an estimate. The X API does not expose when a like happened, only the order. That is why
likedAtis always shown with~.A dead theme is a fossil, not a deletion. It is kept and can be revived. Nothing is removed from the map.
The similarity percentage is not shown to a person. A 0.63 reads as a precision the method does not have.
strength(strong/medium/weak) is used instead; the rawscoreis available for the agent's reasoning.
The full glossary of the method is in docs/DOMAIN.md and can
be queried live with explain_foresight_term.
Documentation
Document | What it is for |
Each tool, with example input and output | |
Contract of the public API it consumes | |
How it is built and why | |
Glossary of the foresight method | |
Deploying remote mode | |
What is never exposed | |
How to add a tool |
License
The code is MIT. The content it serves is not: the signals and the tools4foresight map are paid subscription material.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Trend data, an interactive Trend Radar and ad-targeting dry runs for AI agents. Read-only.
Read-only access to your Citlyze workspace: AI search visibility, citations, and recommendations.
Read-only MCP access to DSGHT.ai published foresight and country-grounded claim resolution.
Search Envisioning's technology research, vocabulary and Hindsight graded forecasts. Read-only.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceProvides read-only access to a personal RAG knowledge base, enabling hybrid search, evidence-grounded retrieval with citations, and knowledge gap tracking for LLM agents.-
- AlicenseNot gradedqualityCmaintenanceEnables clients to search, read, and verify sealed forecasts and public-record cards, inspect resolution calendars, engine strands, sensor alerts, and wire headlines, and check whether stories are independent events or echoes. All access is read-only and requires no key, account, or dependencies.4 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables agents to retrieve structured, pre-published readings of the current geopolitical-risk picture, with in-band freshness and staleness metadata, through a no-auth read-only endpoint.MIT
- AlicenseAqualityBmaintenanceEnables agents to query and explore Prometheus through PromQL, metric and label discovery, alerts, rules, scrape health, and cardinality, while keeping admin writes disabled unless explicitly enabled.1246 npmMIT