# Envisioning (remote · www.envisioning.com)

Search Envisioning's technology research, vocabulary and Hindsight graded forecasts. Read-only.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.envisioning.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-envisioning-mcp/www.md), [page](https://verifymcp.io/servers/com-envisioning-mcp/www)

## Channel facts

- Endpoint: `https://www.envisioning.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 750 tokens (~83/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 18% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Envisioning MCP server?

Envisioning is a hosted endpoint at https://www.envisioning.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-envisioning-mcp 'https://www.envisioning.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-envisioning-mcp": {
      "url": "https://www.envisioning.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-envisioning-mcp": {
      "type": "http",
      "url": "https://www.envisioning.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-envisioning-mcp]
url = "https://www.envisioning.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-envisioning-mcp": {
      "type": "remote",
      "url": "https://www.envisioning.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-envisioning-mcp --url 'https://www.envisioning.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-envisioning-mcp:
    url: "https://www.envisioning.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-envisioning-mcp": {
      "Transport": "http",
      "Url": "https://www.envisioning.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-envisioning-mcp -t streamable-http -u 'https://www.envisioning.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-envisioning-mcp": {
      "type": "http",
      "url": "https://www.envisioning.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 72)

First indexed and scored.

## MCP tools (9)

### `search_site` (~79 tokens)

Search envisioning.com

Search every page on envisioning.com: services, research hubs, technologies, vocabulary terms, reports, case studies, science-fiction origins, newsletter issues and methodology chapters. Returns titles and URLs; read one with get_page.

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `type` (string): Limit to one kind of page

### `get_page` (~71 tokens)

Read a page

Read any envisioning.com page as Markdown, by path: /services, /methodology, /capability, /hindsight, /about, a research hub (/research/<hub>), a report (/observatory/<slug>). Includes the canonical URL and a citation line.

Input parameters:

- `path` (string, required)

### `list_hubs` (~52 tokens)

List research hubs

List Envisioning's research hubs: living collections of emerging technologies per domain (climate, defense, health, quantum and more), each with its technology count. Use a hub slug with search_technologies.

### `search_technologies` (~113 tokens)

Search technologies

Search Envisioning's technology research (over 4,000 technologies across all hubs) by words in the title or summary, optionally within one hub. Each result has a technology readiness level (TRL), impact and investment rating, and its URL. Read one in full with get_technology.

Input parameters:

- `hub` (string): A hub slug from list_hubs
- `limit` (integer)
- `offset` (integer)
- `query` (string): Words to match; omit to list a hub

### `get_technology` (~51 tokens)

Read a technology

Read one technology in full as Markdown: description, ratings, related technologies and sources. Takes the hub and id from search_technologies.

Input parameters:

- `hub` (string, required)
- `id` (string, required)

### `search_vocab` (~58 tokens)

Search the vocabulary

Search Envisioning's AI and machine-learning vocabulary (an encyclopedia of terms, concepts and techniques) by words in the term or its summary.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `query` (string, required)

### `get_vocab_term` (~31 tokens)

Read a vocabulary term

Read one vocabulary term in full as Markdown, by slug from search_vocab.

Input parameters:

- `slug` (string, required)

### `search_hindsight` (~98 tokens)

Search graded forecasts

Search Hindsight: published technology forecasts (IMF, OECD, Gartner, MIT Technology Review, Kurzweil and others) graded against what happened. Search by subject, e.g. 'quantum computing'. Each subject lists its forecasts with publisher, year and verdict. Use it for base rates before you trust a new forecast. Read one forecast with get_hindsight_claim.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `get_hindsight_claim` (~51 tokens)

Read a graded forecast

Read one graded forecast as Markdown: what was predicted, by whom and when, the verdict, the evidence and the citation. Takes a claim id from search_hindsight.

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-envisioning-mcp/www#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72

## Common questions

### What is the Envisioning MCP server?

Envisioning is an MCP server listed in the public MCP registry as com.envisioning/mcp. Search Envisioning's technology research, vocabulary and Hindsight graded forecasts. Read-only. This page covers its hosted endpoint (https://www.envisioning.com/mcp).

### Is the Envisioning MCP server safe to use?

Envisioning scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Envisioning MCP server expose?

Envisioning exposes 9 tools: search_site, get_page, list_hubs, search_technologies, get_technology, and 4 more. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.

### Does the Envisioning MCP server require authentication?

No. We connected to Envisioning without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Envisioning MCP server still maintained?

Envisioning is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Envisioning MCP server?

VerifyMCP ran 13 checks on Envisioning, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.envisioning.com/mcp
- Website: https://www.envisioning.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-envisioning-mcp/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-envisioning-mcp/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-envisioning-mcp/www.json
- HTML version of this page: https://verifymcp.io/servers/com-envisioning-mcp/www
