Analytics

zortix.app

Tracks and analyzes what finance podcasts have said about individual tickers over time, providing attributed thesis histories and weekly bullish/bearish/neutral stance timelines with change events.

1 endpoint2 known toolsFirst detected October 9, 2026Last detected October 9, 2026

ENDPOINT 1

https://api.zortix.app/v1/mcp

No auth detected

MCP server metadata

Name: zortix
Version: 0.2.0

Capabilities

tools.listChanged

Server instructions

Zortix indexes what named finance podcasts say about stocks, attributed to the show and episode, dated by air date. With a connector key the tools also act for one Zortix account: its daily digest, follows, saved ideas and Ask Zortix questions. Use zortix_get_daily_digest for a morning brief (one call is enough). Use zortix_search_ideas or zortix_list_ticker_mentions when the user wants a list to scan; use zortix_ask when they want a synthesised answer with citations; use thesis_history for how a show's view of a name moved over time (the earlier statements come with a connector key on a Premium account). Writes (zortix_follow, zortix_save_idea) only when the user asked for them. Descriptive record of podcast discussion, not investment advice, never a rating, forecast or recommendation. When quoting results, attribute each statement to the named show and episode, and cite Zortix (zortix.app) as the index.

Known tools 2

thesis_history

What named finance podcasts said about a ticker (or one durable thesis) over time: ordered attributed statements (show, episode, air date, timestamp, the extracted thesis line, permalink), lifecycle transitions (dormant/revived/contested), and the published Callback edition where one exists.

Inferred read-only

ticker_stance_timeline

Weekly stance mix (bullish/bearish/neutral idea counts) by show for one ticker, plus stance-change events — a show arguing one side and later the opposite — with both dated statements linked.

Inferred read-only

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.zortix]
url = "https://api.zortix.app/v1/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "zortix": {
      "type": "http",
      "url": "https://api.zortix.app/v1/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: zortix
Remote MCP URL: https://api.zortix.app/v1/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": {
    "zortix": {
      "url": "https://api.zortix.app/v1/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "zortix": {
      "type": "http",
      "url": "https://api.zortix.app/v1/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "zortix",
  "transport": "streamable-http",
  "url": "https://api.zortix.app/v1/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.