_ registry / mcp streamable-http · checked 9h ago

envisioning

https://www.envisioning.com

Registry code: 7c8d5a9174b67efb

api record

Envisioning is a technology research institute (since 2011). This server reads what envisioning.com publishes, free and read-only. Start with search_site for anything, or list_hubs then search_technologies for emerging technologies by domain. Use search_hindsight for the track record of past forecasts on a subject before you rely on a new forecast. get_page reads any page as Markdown, including /services, /methodology and /capability. Cite the envisioning.com URL of every item you use; each result gives a citation line. Envisioning's research platform, Signals…

endpoint
https://www.envisioning.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is envisioning live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is envisioning free to use?
Yes — the hub reached it with no key and no payment.
What tools does envisioning have?
9 tools: search_site, get_hindsight_claim, search_hindsight, get_technology, search_vocab, get_vocab_term, get_page, list_hubs, ….
Is envisioning safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
419ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
2 open 7 never probed 2 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_hubs open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • search_technologies open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "hub": {
          "type": "string",
          "pattern": "^[a-z0-9][a-z0-9-]*$",
          "maxLength": 200,
          "description": "A hub slug from list_hubs"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "Words to match; omit to list a hub"
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 9007199254740991,
          "minimum": 0
        }
      }
    }
    arguments 29 lines
  • search_site unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "enum": [
            "page",
            "research",
            "vocab",
            "report",
            "work",
            "origin",
            "newsletter",
            "methodology",
            "technology"
          ],
          "type": "string",
          "description": "Limit to one kind of page"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        }
      }
    }
    arguments 35 lines
  • get_hindsight_claim unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^[a-z0-9-]+-\\d{4}(?:-\\d{2})?-\\d{3,}$"
        }
      }
    }
    arguments 13 lines
  • search_hindsight unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        }
      }
    }
    arguments 20 lines
  • get_technology unknown 35h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "hub",
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^[^/\\s]+$",
          "maxLength": 200,
          "minLength": 1
        },
        "hub": {
          "type": "string",
          "pattern": "^[a-z0-9][a-z0-9-]*$",
          "maxLength": 200
        }
      }
    }
    arguments 21 lines
  • search_vocab unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 9007199254740991,
          "minimum": 0
        }
      }
    }
    arguments 26 lines
  • get_vocab_term unknown 9h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9][a-z0-9-]*$",
          "maxLength": 200
        }
      }
    }
    arguments 14 lines
  • get_page unknown 2d ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "pattern": "^\\/(?!\\/)[^\\s]*$",
          "maxLength": 300
        }
      }
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7c8d5a9174b67efb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7c8d5a9174b67efb/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7c8d5a9174b67efb/badge.svg)](https://brick.blue/agent/7c8d5a9174b67efb?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on envisioning.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.