DeepStack: Independent analysis of the AI economy
REMOTE · MCP.DEEPSTACK.LTD
Where informed investors disagree, the evidence each side stands on, and the date that settles it.
Available components
Last scanned (8 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1409 tokens (~176/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
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 5 Nov 2026 · Probed https://mcp.deepstack.ltd/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=deepstack.ltd | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bff707f87aeb1227133bbe2643616b22 |
| SANs: deepstack.ltd, mcp.deepstack.ltd, *.mcp.deepstack.ltd | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.deepstack.ltd. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ltd. | present | 54, 4397 | 8, 8 | Verified |
| deepstack.ltd. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.deepstack.ltd/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.deepstack.ltd/mcp | Inconclusive | 405 |
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 →
deepstack_counter The case against a thesis ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The thesis as the user states it, for example “AI demand is real”. |
| limit | integer | – | How many further opposing voices to return after the strongest case. |
No output schema declared.
No examples provided.
deepstack_docket The Docket ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_past | boolean | – | Also list tests dated before today. |
| include_signal | boolean | – | Also list the tests that have no date and resolve on a signal. |
| part | integer | – | Only the tests of one part. |
| status | string | – | – |
| window_days | integer | – | How far ahead to look. |
No output schema declared.
No examples provided.
deepstack_entity A company or a person ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Narrow the lookup to companies, to people or to the organizations that contribute argument (listed with the people). |
| name | string | – | The name, when the slug is not known. |
| slug | string | – | The entity slug, as in https://deepstack.ltd/companies/<slug>/ or /people/<slug>/. |
| ticker | string | – | A listed company’s ticker, for example NVDA. |
No output schema declared.
No examples provided.
deepstack_results Results ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deepstack_search Search DeepStack ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kinds | array | – | Restrict the hits to these kinds; all kinds by default. |
| limit | integer | – | How many hits to return. |
| query | string | yes | Words to look for: a company, a person, a theme, a figure. |
No output schema declared.
No examples provided.
deepstack_sides Who is on each side ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| part | integer | – | The part number, as an alternative to the slug. |
| slug | string | – | The story slug. |
No output schema declared.
No examples provided.
deepstack_story A DeepStack story ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | “summary” leaves out the body paragraphs. |
| part | integer | – | The part number in The Buildout, as an alternative to the slug. |
| slug | string | – | The story slug, as in https://deepstack.ltd/stories/<slug>/. |
No output schema declared.
No examples provided.
deepstack_tape The macro tape ~80
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the DeepStack: Independent analysis of the AI economy MCP server?
DeepStack: Independent analysis of the AI economy is a hosted endpoint at https://mcp.deepstack.ltd/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 · mcp.deepstack.ltd
claude mcp add --transport http mcauduro0-deepstack 'https://mcp.deepstack.ltd/mcp'
What is the DeepStack: Independent analysis of the AI economy MCP server?
DeepStack: Independent analysis of the AI economy is an MCP server listed in the public MCP registry as io.github.mcauduro0/deepstack. Where informed investors disagree, the evidence each side stands on, and the date that settles it. This page covers its hosted endpoint (https://mcp.deepstack.ltd/mcp).
Is the DeepStack: Independent analysis of the AI economy MCP server safe to use?
DeepStack: Independent analysis of the AI economy scores 71 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 DeepStack: Independent analysis of the AI economy MCP server expose?
DeepStack: Independent analysis of the AI economy exposes 8 tools: deepstack_search, deepstack_story, deepstack_sides, deepstack_docket, deepstack_results, and 3 more. Their descriptions and schemas cost roughly 1,021 tokens of context every time the server is loaded.
Does the DeepStack: Independent analysis of the AI economy MCP server require authentication?
No. We connected to DeepStack: Independent analysis of the AI economy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DeepStack: Independent analysis of the AI economy MCP server still maintained?
DeepStack: Independent analysis of the AI economy is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.