Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
DeepStack: Independent analysis of the AI economy is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Where informed investors disagree, the evidence each side stands on, and the date that settles it.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http deepstack-independent-analysis-of-the-ai-econ-mcp https://mcp.deepstack.ltd/mcp
# 2 — ask your agent for something these tools do
# deepstack_search, deepstack_story, deepstack_sides and 5 more
DeepStack: Independent analysis of the AI economy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MCAll 1 server
mcauduro01 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http deepstack-independent-analysis-of-the-ai-econ-mcp https://mcp.deepstack.ltd/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to look for: a company, a person, a theme, a figure. |
| limit | integer | no | How many hits to return. |
| kinds | array | no | Restrict the hits to these kinds; all kinds by default. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | The story slug, as in https://deepstack.ltd/stories/<slug>/. |
| part | integer | no | The part number in The Buildout, as an alternative to the slug. |
| detail | string | no | “summary” leaves out the body paragraphs. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | The story slug. |
| part | integer | no | The part number, as an alternative to the slug. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window_days | integer | no | How far ahead to look. |
| include_past | boolean | no | Also list tests dated before today. |
| include_signal | boolean | no | Also list the tests that have no date and resolve on a signal. |
| status | string | no | — |
| part | integer | no | Only the tests of one part. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | The entity slug, as in https://deepstack.ltd/companies/<slug>/ or /people/<slug>/. |
| ticker | string | no | A listed company’s ticker, for example NVDA. |
| name | string | no | The name, when the slug is not known. |
| kind | string | no | Narrow the lookup to companies, to people or to the organizations that contribute argument (listed with the people). |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim | string | yes | The thesis as the user states it, for example “AI demand is real”. |
| limit | integer | no | How many further opposing voices to return after the strongest case. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DeepStack: Independent analysis of the AI economy or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.1 · scanned 24 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest3e98f2bc8e2be572f0267dba581e49d3792d710962dbfb1335230b91614c627d
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| deepstack_search | no tags | |
| deepstack_story | no tags | |
| deepstack_sides | no tags | |
| deepstack_docket | no tags | |
| deepstack_results | no tags | |
| deepstack_entity | no tags | |
| deepstack_tape | no tags | |
| deepstack_counter | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3e98f2bc8e2be572
Scanned2026-10-24
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DeepStack: Independent analysis of the AI economy can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.