Markets MCP

Name: Markets MCP
Author: worldclasstom

作者：worldclasstom版本 1.8.0i★ –i在云端运行

注册名称markets.tally/mcp

安装

概览

作者提供的说明（英文原文）

AI risk officer: private trading theses, evidence, exit criteria and decision history. No execution.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 会计、财务与税务

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://tally.markets/api/mcp

在终端中运行这条命令

claude mcp add --transport http tally https://tally.markets/api/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "tally": {
      "url": "https://tally.markets/api/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "tally": {
      "type": "http",
      "url": "https://tally.markets/api/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://tally.markets/api/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过域名 tally.markets 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“会计、财务与税务”中的其他服务器比较i

星标数多于此分类中其他 1734 个服务器的 0%
发布到注册中心的时间比此分类中其他 1734 个服务器的 70% 更新
基础检查结果等于或优于此分类中其他 1734 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Markets MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.8.0）于16天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Finance Toolkit, SolidInvoice, Korea Tax Calculator

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Finance Toolkit

作者：JerBouma

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

电脑或云端★ 5,496MIT今天更新

安装

SolidInvoice

作者：SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

在云端运行★ 981MIT8天前更新

安装

Korea Tax Calculator

作者：UpstageAI

Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.

在你的电脑上运行★ 97MIT昨天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Tally MCP

Your AI risk officer for AI-assisted trading. Tally keeps your private thesis, evidence, risk budget, exit criteria and decision history across conversations in Claude, ChatGPT and other compatible MCP clients.

Connect

See the setup guide. Endpoint: https://tally.markets/api/mcp, Streamable HTTP with OAuth. Tool availability depends on the AI app, plan and workspace permissions.

Start with: “Get started with Tally, then run my checkup.”

Free includes 3 active theses (including drafts) and 10 total created. Closing frees an active slot but does not reset the total. Saved records remain readable, reviewable and closable. Sentinel is $9/month or $49/year with no creation cap and supported monitoring across the active journal.

Connected is an optional $89/month tier adding read-only broker snapshots after payment, provider activation and explicit owner consent. Every plan includes the AI connection. If a paid customer's broker service is awaiting initial setup, get_checkup.brokerage.status is activation_pending; explain that state and continue the journal workflow. A Tally check time is separate from provider data freshness. Transaction history can be delayed; this is not a live trading feed.

Tools

Tool	Purpose
`get_execution_evidence`	Read archived orders, fills and decisions for an optional Propr account; no live protection claim
`get_started`	Current discipline protocol and tool boundaries
`get_checkup`	Active theses, evidence, deadlines, issues and history; optional read-only Connected broker snapshots or Propr state
`list_theses`, `get_thesis`	Private journal records
`create_thesis`	Save a thesis and criteria; enforce the shared free allowance
`arm_thesis`	Change journal readiness after optional cooling-off; no trade authorization
`record_reading`	Add sourced evidence to the record
`record_decision_event`	Save a user-approved step, decision, personal boundary, rule deviation or linked correction
`get_decision_history`	Read session entries and watcher records chronologically, with source labels and pagination
`submit_product_feedback`	Send the user’s chosen product feedback to the Tally team
`fire_criterion`	Record an objectively triggered criterion
`close_thesis`	Close the journal record, with a reason; no brokerage execution
`get_receipt_link`	Retrieve an explicitly published receipt link
`declare_mandate`, `log_agent_activity`	Preserve optional mandate/activity records; never control trading

The morning-checkup, pre-register-trade and close-out prompts support reviews. Scheduling is client-dependent, not a guarantee of unattended operation. Keep user confirmation controls in place.

Execution boundary

No connector tool places, cancels, closes or modifies orders, changes protective stops, or resumes autonomous trading. Existing optional Propr controls remain in Tally Settings. Journal closure must never be represented as position closure. OpenAI execution capabilities remain disabled under current policy guidance.

Records are owner-scoped and private unless the user explicitly publishes a receipt. Read privacy and terms.

This repository contains public documentation and registry metadata only. Server implementation and secrets are not published here. Method: 2026-10-21.1. Server manifest: 1.8.0 (publication is a separate release step).

In get_checkup, brokerage is null without an eligible Connected subscription; it can describe activation pending before a broker is connected. The retired monitoring section is null. The optional agent section is null without a Propr account. Journal users do not need either connection.

Transport safeguards: requests are limited to 128 KiB before JSON parsing, and tool arguments to 5,000 combined object keys/array entries. Split larger evidence updates into smaller calls. Each request gets its own MCP server instance.

Decision history

With the user’s agreement, save a concise sequence of what happened, what they decided, why, and which rule they followed or crossed. A boundary entry states the user’s line in the sand and their intended response. Corrections append and link to an earlier event. This works on every plan and does not consume a thesis slot.

Use get_decision_history alongside checkup data for process reviews. Records are oldest first; follow next_cursor until null for a complete period. Keep filters unchanged between pages. Date-range queries combine user reports and watcher alerts/readings; a session filter returns reported entries only because watcher records have no inferred session assignment. occurred_at and recorded_at distinguish an event from a retrospective report.

Tally does not receive the full Claude or ChatGPT transcript. Save only relevant summaries the user approved. Do not infer mental health, label a trading style from a small sample, or mistake a reported decision for a verified fill. Compare process with the rule that existed at the time, separately from P&L. Review possible tipping points with the user; a boundary entry does not control execution.

Product feedback is separate: show the exact feedback wording, get the user’s agreement to send it to Tally’s team, then call submit_product_feedback. Never include private journal content by default. Signed-in users can also use Feedback in their app footer.