Envisioning
REMOTE · WWW.ENVISIONING.COM
Search Envisioning's technology research, vocabulary and Hindsight graded forecasts. Read-only.
Available components
Last scanned (16 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 750 tokens (~83/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.envisioning.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.envisioning.com | CN=YR2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 614a6cf24915844be7da544dcd2fc07075c |
| SANs: www.envisioning.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.envisioning.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| envisioning.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self' vercel.live https://research-envisioning.vercel.app; script-src 'self' 'unsafe-inline' cdn.vercel-insights.com vercel.live va.vercel-scripts.com unpkg.com res.cloudinary.com plausible.io https://challenges.cloudflare.com https://research-envisioning.vercel.app; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://research-envisioning.vercel.app; img-src 'self' res.cloudinary.com media.envisioning.workers.dev media.envisioning.com www.datocms-assets.com substackcdn.com substack-post-media.s3.amazonaws.com media.licdn.com research-envisioning.vercel.app img.youtube.com i.ytimg.com pbs.twimg.com abs.twimg.com blob: data:; media-src youtube.com res.cloudinary.com media.envisioning.workers.dev media.envisioning.com blob:; connect-src *; font-src 'self' data: fonts.gstatic.com https://research-envisioning.vercel.app; worker-src 'self' blob:; child-src 'self' blob: https://challenges.cloudflare.com; frame-src 'self' vercel.live https://newsletter.envisioning.io https://www.youtube |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.envisioning.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.envisioning.com/mcp | HTTPS enforced | 308 | https://www.envisioning.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_hindsight_claim Read a graded forecast ~51
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_page Read a page ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
get_technology Read a technology ~51
Read one technology in full as Markdown: description, ratings, related technologies and sources. Takes the hub and id from search_technologies.
| Name | Type | Req | Description |
|---|---|---|---|
| hub | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_vocab_term Read a vocabulary term ~31
Read one vocabulary term in full as Markdown, by slug from search_vocab.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_hubs List research hubs ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_hindsight Search graded forecasts ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_site Search envisioning.com ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| type | string | – | Limit to one kind of page |
No output schema declared.
No examples provided.
search_technologies Search technologies ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hub | string | – | A hub slug from list_hubs |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | Words to match; omit to list a hub |
No output schema declared.
No examples provided.
search_vocab Search the vocabulary ~58
Search Envisioning's AI and machine-learning vocabulary (an encyclopedia of terms, concepts and techniques) by words in the term or its summary.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · www.envisioning.com
claude mcp add --transport http com-envisioning-mcp 'https://www.envisioning.com/mcp'
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.