Skip to content

DeepStack: Independent analysis of the AI economy MCP server

io.github.mcauduro0/deepstackmcauduro0streamable-httpv1.0.1Scanned

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

8 tools: 7 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 7 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DeepStack: Independent analysis of the AI economy MCP server can do

The DeepStack: Independent analysis of the AI economy MCP server is published by the GitHub account mcauduro0. It has 8 tools. It can create or change data (7 tools: deepstack_story, deepstack_sides, deepstack_docket, deepstack_results and 3 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 7Claude Code: ask
  • deepstack_counterUse when the user states a thesis or a claim about the AI economy and wants the strongest case against it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: The case against a thesis
  • deepstack_docketUse when the user asks what will decide a dispute, what to watch, or the next dated test.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: The Docket
  • deepstack_entityUse when the user asks what the voices argued about a company, or what a person argued, in The Buildout; by slug, ticker or name.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: A company or a person
  • deepstack_resultsUse when the user asks what resolved and how the Call fared.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Results
  • deepstack_sidesUse 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Who is on each side
  • deepstack_storyUse 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 c…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: A DeepStack story
  • deepstack_tapeUse 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 natura…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: The macro tape
Only reads 1Show 1 read-only tool

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.deepstack.ltd/mcp: tools/list returned 8 tools to an anonymous client, including deepstack_story (write), deepstack_sides (write), deepstack_docket (write), deepstack_results (write), deepstack_entity (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http deepstack https://mcp.deepstack.ltd/mcp
claude mcp add --transport http deepstack https://mcp.deepstack.ltd/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__deepstack__deepstack_search"
    ],
    "ask": [
      "mcp__deepstack__deepstack_story",
      "mcp__deepstack__deepstack_sides",
      "mcp__deepstack__deepstack_docket",
      "mcp__deepstack__deepstack_results",
      "mcp__deepstack__deepstack_entity",
      "mcp__deepstack__deepstack_tape",
      "mcp__deepstack__deepstack_counter"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as deepstack. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.mcauduro0/deepstack/verify?hash=b4781d96456dc22aaf422e1e05cc66a2d114a280a75c994c379cedde99f391de" | jq -e '.changed == false'

Pinned hash b4781d96456d, from Nov 20, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.mcauduro0/deepstack/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.mcauduro0/deepstack
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mcauduro0/deepstack.svg)](https://radar.anlyon.com/servers/io.github.mcauduro0/deepstack)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:39 UTC.

DeepStack: Independent analysis of the AI economy MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DeepStack: Independent analysis of the AI economy MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DeepStack: Independent analysis of the AI economy MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DeepStack: Independent analysis of the AI economy MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DeepStack: Independent analysis of the AI economy MCP server have?

8 tools: 7 write, 1 read. deepstack_story, deepstack_sides, deepstack_docket, deepstack_results, deepstack_entity, deepstack_tape, deepstack_counter and deepstack_search.

Does the DeepStack: Independent analysis of the AI economy MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DeepStack: Independent analysis of the AI economy MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DeepStack: Independent analysis of the AI economy MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.