原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Tapebasis

作者:giraygokirmak版本 1.2.1i★ 0i在你的电脑上运行代码仓库 ↗
注册名称io.github.giraygokirmak/tapebasis

安装方法

What it does

Market data from multiple independent providers, compared with clear provenance.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 会计、财务与税务

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度14/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分26/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 13 (只用于“上升中”标签)

安装

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

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 打开电脑版 Claude 应用的设置文件

    SettingsDeveloperEdit Config

  3. 粘贴这些设置并保存文件

    正在检查命令 · 通过后才会显示复制按钮

  4. 退出 Claude 再重新打开

  5. 试一试

    用 Tapebasis 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Tapebasis,或回答中出现 Tapebasis 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Tapebasis

Tapebasis 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 Tapebasis 的应用

  • 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
  • 需要先在电脑上安装 Node.js(只需一次)
  • 需要先在电脑上安装 Node.js(只需一次)
  • 需要先在电脑上安装 Node.js(只需一次)

B · 会计、财务与税务 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    正在检查命令 · 通过后才会显示复制按钮

  4. 在 Claude Code 中输入 /mcp

    应能看到 Tapebasis 在列表中并显示已连接

  5. 试一试

    用 Tapebasis 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Tapebasis,或回答中出现 Tapebasis 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 点击这个按钮打开 Cursor

    正在检查命令 · 通过后才会显示复制按钮

  3. 在 Cursor 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 Tapebasis 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Tapebasis,或回答中出现 Tapebasis 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 点击这个按钮打开 VS Code

    正在检查命令 · 通过后才会显示复制按钮

  3. 在 VS Code 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 Tapebasis 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Tapebasis,或回答中出现 Tapebasis 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Tapebasis 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

安装在电脑上

Claude Code

正在检查命令 · 通过后才会显示复制按钮

Claude Desktop (claude_desktop_config.json)

正在检查命令 · 通过后才会显示复制按钮

Cursor (~/.cursor/mcp.json)

正在检查命令 · 通过后才会显示复制按钮

VS Code (mcp.json)

正在检查命令 · 通过后才会显示复制按钮

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

一览

每周下载量i
427/周
连接方式
在你的电脑上运行
最新版本i
1.2.1
发布到注册中心i
2026年11月19日
代码最后更新i
2026年11月19日
作者
giraygokirmak
软件包
npm: tapebasis
pypi: tapebasis
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 giraygokirmak 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

尚未检查

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/giraygokirmak-tapebasis.svg)](https://mcp.popnx.com/en/servers/giraygokirmak-tapebasis)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

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

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

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

常见问题

Tapebasis 安全吗?

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

它需要哪些密钥或代码?

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

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

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(1.2.1)于今天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Python (uv)。

有什么可以替代它?

同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

SolidInvoice

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

作者:SolidInvoice正在增长★ 99110天前更新

在云端运行✓ 服务方 · solidinvoice.co

Signal8

SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.

作者:signal8ai正在增长↓ 431/周★ 42510天前更新

电脑或云端✓ 服务方 · signal8.ai

Journalit

Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.

作者:Cursivez正在增长★ 26111天前更新

在云端运行✓ 服务方 · journalit.co

Beancount.io

Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.

作者:bex-co正在增长★ 702 整个仓库的星标44天前更新

在云端运行✓ 服务方 · beancount.io
与相似项目对比
本项
Tapebasis
SolidInvoiceSignal8JournalitBeancount.ioTapetide - Indian Stock Market MCP
运行位置需要安装在电脑上在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否是否否是
可在 Claude 中按 + 添加否否否否否否
基础检查3/34/65/54/44/45/5
许可证MITMITMITNOASSERTIONMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

Multiple tapes, one basis. An MCP server that serves TradingView, Finviz, Yahoo Finance, StockAnalysis and Bloomberg market data together, cross-checks every overlapping figure, and labels each response with the provider that actually produced it.


*Basis* is the finance term for the price difference between two markets quoting the same asset. *Tape* is the ticker tape. Tapebasis is the spread between multiple feeds, measured on every call: zero when they agree, reported when they don't.

The point is redundancy you can *see*. Every provider that could answer a field is asked, natively in parallel. When several answer, the data is cross-checked. When only one answers, you get the data, clearly marked as single-source. When none answers, you get NONE instead of a plausible-looking number. And because every provider scrapes or calls an undocumented upstream, a background monitor probes every endpoint and reports API/schema drift inside ordinary tool responses.

Each provider is fetched natively: TradingView's own scanner and chart websocket, Finviz's HTML and JSON islands, Yahoo's chart API, StockAnalysis's quote API, Bloomberg's quote pages. No leg proxies another: a provider that quietly forwards a competitor's numbers is worthless as a cross-check.

Bloomberg and StockAnalysis are the other two legs, asked like the rest, in parallel, on the same call. The properties that make each of them different from a plain live feed are reported rather than hidden by a tolerance. Bloomberg's equity and index prints are exchange-delayed (exchangeDelay is 15 Minutes), so a pair of prints further apart than the print-time guard allows is reported as not comparable with the delay named, instead of being called a provider disagreement; it also never wins the freshness tie-break against a live print. Its static fields are penny-identical to Yahoo's, so agreement between those two is weak corroboration, not two independent witnesses. What it adds is its own quote pages and the government benchmark yield curve, which no other provider here publishes. StockAnalysis covers US equities and ETFs only, and its quote surface is the same consolidated tape Yahoo serves, so that pair is weak corroboration for the same reason; indices, FX, crypto, commodities and foreign listings are reported as not carried instead of requested.


The data_provider contract

Every tool result carries exactly one of eight values. It states coverage, never agreement:

ValueMeaning
ALLEvery provider that was asked answered. Coverage is complete for this call.
PARTIALMore than one answered, but a provider that was asked produced nothing. The values are served; errors says why the missing leg is missing.
TRADINGVIEWOnly TradingView answered. Served, but not corroborated.
FINVIZOnly Finviz answered. Served, but not corroborated.
YAHOOOnly Yahoo Finance answered. Served, but not corroborated.
SAOnly StockAnalysis answered. Served, but not corroborated; US equities and ETFs only.
BLOOMBERGOnly Bloomberg answered. Served, but not corroborated; its quote can be delayed.
NONENo provider could supply it. No value is presented.

ALL means "every provider asked answered", not "they agree". Agreement is a separate axis, and it lives in comparisons[].match. A provider that was asked and failed makes the response PARTIAL, never ALL: the label describes coverage, and a listed error is missing coverage. providers_answered names exactly which providers contributed. The positive agreement notice appears only after a real agreeing comparison. Invalid pairs keep their readings, match: null and a not_comparable reason; a resolved symbol that returns no data is NO_DATA, not NOT_ATTEMPTED.

The same envelope also contains:

{

"data_provider": "ALL", "verification": "MULTI_SOURCE", // MULTI_SOURCE | SINGLE_SOURCE | UNAVAILABLE "providers_answered": ["TRADINGVIEW", "FINVIZ", "YAHOO", "SA", "BLOOMBERG"], "notice": "Every provider asked answered (TradingView, Finviz, Yahoo Finance, StockAnalysis and Bloomberg). ...", // names whichever answered "data": { ... }, // the reconciled payload, one value per field "fields": { // per-field provenance, never a joint label "price": { "source": "FINVIZ", "supplied": ["TRADINGVIEW", "FINVIZ", "YAHOO", "SA"], "compared": ["TRADINGVIEW", "FINVIZ", "YAHOO", "SA"], "agreement": true }, "peers": { "source": "FINVIZ", "supplied": ["FINVIZ"], "compared": [], "agreement": null } }, "freshness": { // why data holds the value it does "tradingview": "2026-11-04T00:59:53+00:00", "finviz": "2026-11-04T10:42:00+00:00", "yahoo": "2026-11-03T21:00:01+00:00", "sa": "2026-11-03T21:00:01+00:00", // same consolidated tape as Yahoo "bloomberg": "2026-11-04T10:27:00+00:00", // 15 min behind, so it cannot win "chosen": "FINVIZ", "decision": "newest", // newest | tie | no_timestamp "newest_print": "2026-11-04T10:42:00+00:00", "reason": "FINVIZ printed most recently (2026-11-04T10:42:00+00:00)" }, "comparisons": [ // the actual side-by-side numbers { "field": "price", "values": { "TRADINGVIEW": 331.9, "FINVIZ": 332.33, "YAHOO": 331.9, "SA": 331.9, "BLOOMBERG": 332.1 }, "match": true, "diff_pct": 0.1294, "tolerance_pct": 0.5, "pairs": [ { "between": ["TRADINGVIEW", "FINVIZ"], "match": true, "diff_pct": 0.1294 }, ... ], "chosen": "FINVIZ" } ], "resolutions": { "TRADINGVIEW": { "symbol": "NASDAQ:AAPL", ... }, ... }, "sources": { "TRADINGVIEW": "scanner.tradingview.com", "FINVIZ": "...", "YAHOO": "...", "SA": "...", "BLOOMBERG": "..." }, "errors": [ { "provider": "FINVIZ", "code": "...", "message": "..." } ], "warnings": [ "..." ], "degraded": false, // true when the health monitor saw drift/downtime "generated_at": "2026-11-04T10:43:02+00:00" }

One price, and it is the newest print. Every provider that can supply a field is asked. data holds exactly one value per compared field: the reading whose market print is newest. Providers that share the newest instant are the only tie-break candidates, and the documented default order (FINVIZ, TRADINGVIEW, YAHOO, SA, BLOOMBERG) picks between them; Bloomberg is last precisely because its print can be structurally older, and StockAnalysis sits just before it because its coverage is the narrowest of the live feeds. freshness.decision is the machine-readable outcome (newest, tie, no_timestamp), so a caller never has to parse the sentence in reason. Every original reading stays in comparisons.values.

Disagreements are never silently resolved. If the providers report different prices, all values stay in comparisons, the field is named in notice and warnings, and data_provider stays ALL (every asked provider *did* answer; they just disagree). The single value in data is the newest print, and the notice says so.

A field measured against a session baseline is not compared across observations. A day-change percentage or a session volume is derived from the previous close of the session the print belongs to. Finviz in a pre-market session and Yahoo at the prior close will legitimately differ, so such a pair is reported as not_comparable (with the reason in pairs[].not_comparable) instead of being called a provider conflict. Four guards decide that: a 900 s print-time ceiling, equality of the US/Eastern session date even when the prints are seconds apart, a declared feed delay as a boundary of its own (Bloomberg states 15 minutes on equities, so its pairs stop being comparable at that distance), and, for the fields re-derived from the print, an 8 h age ceiling against the clock so a feed that froze with its peers cannot pass. Both readings still appear; the field is listed in warnings as not cross-checked.

Some fields have no shared definition at all. Spot FX has no single official previous close, so each provider derives its own daily roll and the day-change figures answer different questions. On FX, change_percent is therefore always reported from every provider but never compared, with that reason in the pair. Instrument-level, not provider-level: no tolerance can make it a conflict.

A price is a print, and it carries its session. The obvious price field goes stale as soon as the regular session ends: TradingView's scanner close stops moving while its premarket_close keeps streaming, Yahoo's regularMarketPrice freezes while fulldayPrice does not, and StockAnalysis keeps the current extended print in extended_hours. Each provider's live print is therefore resolved before anything is compared, and stock_quote / stock_prices publish the session it belongs to (pre_market, regular, post_market, overnight) with the day change and previous close measured against that same session's baseline, recovered from the print's own change. The label follows the print that was served rather than a nominated leg, so a delayed feed cannot name a session the served number does not belong to. stock_extended_hours independently reads Blue Ocean overnight prints from TradingView's BOATS: socket and Yahoo's quote header. overnight_source names the newest eligible print, while overnight_readings, overnight_comparison and overnight_errors retain provenance and failures. On the same overnight occurrence, the normalized change uses Yahoo's reference_close; TradingView's venue-based change is retained separately as reported_change and reported_change_percent. An absent or cross-occurrence reference leaves the normalized change null. Last night's print survives after 04:00 ET with is_current: false, rather than being passed off as the live pre-market price. stock_quote does not carry overnight itself; use stock_extended_hours.

Extended-hour freshness is pairwise: Yahoo's candle time is parseable UTC ISO, StockAnalysis supplies price_timestamp, and TradingView's regular update_time is never attached to its separate extended print. An undated print therefore leaves only its own pairs not_comparable; a dated Yahoo/StockAnalysis pair can still agree. after_hours_readings retains each provider's price, session, timestamp, baseline and derived change, so the number's definition is visible beside it.

Implementation: reconcile.py (fan-out + comparison), freshness.py (print-time parsing), sessions.py (which session a print belongs to, and which print is live), providers_state.py (envelope + labels).


Symbols are resolved per provider

The same instrument is spelled differently by each upstream, and the differences are not mechanical:

| Instrument | TradingView | Finviz | Yahoo Finance | StockAnalysis | Bloo

只显示了开头部分;其余内容请在仓库中阅读