# DeepStack: Independent analysis of the AI economy

> Where informed investors disagree, the evidence each side stands on, and the date that settles it.

- name: io.github.mcauduro0/deepstack
- version: 1.0.1
- connection class: R0 (autonomous)
- trust: 97/100
- quality: 89/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.mcauduro0%2Fdeepstack
- tools: https://api.protogrid.dev/v1/servers/io.github.mcauduro0%2Fdeepstack/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% +updated-0d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,653 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 0 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 1,653 tokens to load them all
- tool set hash: 81caa24117791305b8a533361312403f
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.mcauduro0/deepstack.svg)](https://protogrid.dev/servers/io.github.mcauduro0/deepstack)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.deepstack.ltd/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (8)

- `deepstack_counter`: Use when the user states a thesis or a claim about the AI economy and wants the strongest case against it. Returns the side the claim sits on (or the question, when no side label fits), the strongest case against that side from a voice outside it, dated and linked, more opposing voices, and the dated tests that settle it; below the relevance floor, that DeepStack has no formed side on the claim.
- `deepstack_docket`: Use when the user asks what will decide a dispute, what to watch, or the next dated test. Returns the dated tests that will settle each story, from today forward: date and precision, status, the event, the resolver (which series, release or earnings print decides it) and the story, each with its URL.
- `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. Returns where it appears, the figures the stories reported, each argument attributed, dated and linked, and for a listed company the delayed market snapshot with its source. Never a score or a ranking.
- `deepstack_results`: Use when the user asks what resolved and how the Call fared. Returns the tests that came in: verdict, what happened with the primary source and the number, what it did to the Call, and the rule that no hit rate is shown until ten results exist.
- `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. Use it first when the slug or name is not known.
- `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. Returns, for one story by slug or part number, The DeepStack Call and its side, every attributed, paraphrased voice on each side with its date and source link, the strongest case against each side, where voices cross, and the dated tests that settle it.
- `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_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.