INDIVIDUAL MCP TOOL

deepstack_results

Use when the user asks what resolved and how the Call fared.

deepstack.ltdnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.deepstack.ltd/mcp

No auth detected

Connect to this endpoint to inspect the live schema for deepstack_results and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

deepstack.ltd

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.deepstack-mcp]
url = "https://mcp.deepstack.ltd/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "deepstack-mcp": {
      "type": "http",
      "url": "https://mcp.deepstack.ltd/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: deepstack-mcp
Remote MCP URL: https://mcp.deepstack.ltd/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "deepstack-mcp": {
      "url": "https://mcp.deepstack.ltd/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "deepstack-mcp": {
      "type": "http",
      "url": "https://mcp.deepstack.ltd/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "deepstack-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.deepstack.ltd/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

deepstack_search — Use when the user asks where informed investors disagree on a topic of the AI economy, or wants DeepStack’s published analysis on a company, a person or a question; returns the matching stories, sides, tests and entities with their canonical URLs, or answers “DeepStack has no formed side on …” with up to three nearest items, labeled as nearest.
deepstack_story — Use when the user wants one Part of The Buildout read in full, by slug or part number: headline, dek, The DeepStack Call (stance, conviction, three actions, what would change the call, the side it takes and the case against it, the next dated test), key numbers, the full text as plain paragraphs, the dated tests, any result, the companies and people named, and the sources, each with its URL.
deepstack_sides — Use when the user asks for the bull and bear case, who disagrees with a thesis, the counter-argument, or what would change a side’s mind.
deepstack_docket — Use when the user asks what will decide a dispute, what to watch, or the next dated test.
deepstack_entity — Use when the user asks what the voices argued about a company, or what a person argued, in The Buildout; by slug, ticker or name.
deepstack_tape — Use when the user asks for the macro figures DeepStack tests its notes against, each with its producer and date: Treasury yields, the real yield, the S&P 500, VIX, Brent, US natural gas, copper, the Fed funds target, CPI and payrolls, with the weekly change and the as-of time of each series.
deepstack_counter — Use when the user states a thesis or a claim about the AI economy and wants the strongest case against it.