SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Point-in-time exchange trading rules with sources: A-share price limits, stamp duty, ticks, futures
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 16/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Marina rules。按照 https://mcp.popnx.com/i/david-marina-marina-rules.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月16日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Marina rules,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "marina-rules": { "command": "uvx", "args": [ "marina-rules", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Marina rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"marina-rules": {
"command": "uvx",
"args": [
"marina-rules",
"mcp"
]
}
}
}用 Marina rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Marina rules,或回答中出现 Marina rules 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Marina rules
Marina rules 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Marina rules 的应用
B · 会计、财务与税务 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Marina rules,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user marina-rules -- uvx marina-rules mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Marina rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user marina-rules -- uvx marina-rules mcp应能看到 Marina rules 在列表中并显示已连接
用 Marina rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Marina rules,或回答中出现 Marina rules 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Marina rules,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "marina-rules": { "command": "uvx", "args": [ "marina-rules", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Marina rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Marina rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Marina rules,或回答中出现 Marina rules 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Marina rules,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "marina-rules": { "type": "stdio", "command": "uvx", "args": [ "marina-rules", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Marina rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Marina rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Marina rules,或回答中出现 Marina rules 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user marina-rules -- uvx marina-rules mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"marina-rules": {
"command": "uvx",
"args": [
"marina-rules",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"marina-rules": {
"command": "uvx",
"args": [
"marina-rules",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"marina-rules": {
"type": "stdio",
"command": "uvx",
"args": [
"marina-rules",
"mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 David-Marina 验证,该账户拥有此仓库
代码最后更新于4天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 marina-rules@2026.11.16 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/david-marina-marina-rules)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于4天前,最新版本(2026.11.16)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
48 tools for ~8,000 NSE & BSE stocks: quotes, screener, financials, filings, FII/DII, options
| 本项 Marina rules | SolidInvoice | Signal8 | Journalit | Beancount.io | Tapetide - Indian Stock Market MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 是 | 否 | 否 | 是 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/6 | 5/5 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Auditable backtests: the exchange trading rules in force on each day, as data with sources.
Price limits, fees, trading sessions, ticks, settlement — every record says *when* a rule took effect and *where* it was published. A backtest asks for the rule of each trade date instead of hard-coding today's; marina-check then verifies every fill against the rules of its day and, on a strict pass, emits a stamp that anyone holding the same fill log and the same rules version can recompute; citation() names the exact, byte-pinned rules a result ran under.
What a stamp certifies is deliberately narrow: the fills respected these rules. It says nothing about look-ahead in prices, survivorship or overfitting. as_of closes one more gap: it answers only from rules that had been published by a given date, so a backtest cannot use a rule change before it was announced (a rule whose publication date was not located is refused, not assumed).
Use it to check that a backtest applied the rules in force on each day — China A-share daily price limits (limit-up / limit-down), stamp duty and transfer fees, tick sizes and sessions; futures margins, limits and fees; Hong Kong and US equity rules — and to validate a fill log against them (marina-check). It holds rules only: no prices, index constituents, ST or suspension lists, adjustment factors or trading calendars.
中文 · 市场交易规则的「tzdata」:涨跌幅、费用、交易时段、tick 等制度从哪天起、依据什么,每条记录都带官方原文出处、引文和内容哈希。它给回测引擎和 AI Agent 用——查不到就报错,不猜;
coverage()预检整段窗口,resolve()返回统一判定,diff_rules告诉你升级后哪些回测要重跑。目前覆盖 A 股、中金所股指期货与国债期货、上期所 / 上期能源 / 郑商所 / 广期所商品期货(自 2024 年起)、港股和美股;大商所尚未覆盖,各市场的具体范围见 Coverage。CC0 数据 + MIT 代码。中文入门:README.zh-CN.md。
rules: marina-rules@2026.11.16 sha256:80188ec249ce22ae
Marina is to trading rules what the tz database is to time zones and what exchange_calendars is to trading days: small, boring, free, and meant to be the one copy everyone imports instead of the thousand copies everyone gets slightly wrong.
Status: 2026.11.16. 2873 records — 1421
verified, 1451single-source, 1unverified— each traced to primary sources with quotes and content hashes. Maturity differs by market: China A-share, CFFEX, SHFE and INE records are mostlyverified; CZCE, GFEX, Hong Kong and US records are mostlysingle-source— a first pass, to be read as such (counts per market, what the levels mean). China A-shares: price limits, fees, sessions, ticks and holding periods, measured from 2006-07-01; CFFEX stock-index futures from 2010; CFFEX treasury bond futures from 2013; SHFE (20 products, incl. night sessions), INE (5 products), CZCE (27 products, mostlysingle-source) and GFEX (5 products, no sessions yet): margin, price limits, fees and same-day round trips from 2024-01-01; Hong Kong shares and ETFs from 2010; US stocks and ETFs from 2010. DCE, crypto and other markets are not covered. Details per market: Coverage. Treat the exchange's own notice as authoritative, always.
What changed in each release, and which backtests a release asks you to re-run: CHANGELOG.md.
Every backtest engine, every trading agent, and every research notebook re-implements the same handful of rules — "ChiNext limit is 20%" — and a large share of them get the *date* wrong (it was 10% before 2020-08-24), the *scope* wrong (ST stocks differ), or the *rounding* wrong (exchanges round half-up; round() doesn't). These errors used to live in one firm's code. Now that AI agents write backtests by the thousand, the same error gets copied by the thousand.
A shared, cited, versioned table fixes this the way tzdata fixed time zones: not by being authoritative, but by being the same for everyone and traceable to the source.
examples/hardcoded_vs_marina.py prints six such fills side by side — the number a backtest gets from today's rule, and the number that applied on the trade date:
| fill | hard-coded with today's rule | rule of that day |
|---|---|---|
| ChiNext, 2020-08-21, previous close 10.00: limit-up / limit-down | 12.00 / 8.00 | 11.00 / 9.00 |
| ST main-board stock, 2024-06-14, previous close 10.00 | 11.00 / 9.00 | 10.50 / 9.50 |
| Main-board IPO in its first five days, 2024-01-30 | 11.00 / 9.00 | no limit |
| Sell 100,000 on 2008-04-23: stamp duty + transfer fee | 51.00 | 302.55 |
| Sell 100,000 on 2023-08-25 | 51.00 | 101.00 |
pip install marina-rules # self-contained: the dataset ships inside the wheel, byte-pinned
import marina_rules as mr
mr.rule_at("stamp_duty_sell", "2023-08-28") # 0.0005 mr.rule_at("price_limit_pct", "2020-08-23", "chinext", "XSHE") # 0.10 mr.limit_price(10.00, "chinext", "2021-03-01", "XSHE") # (12.0, 8.0) — exchange rounding mr.limit_price(10.00, "ipo_first5_main", "2024-01-30", "XSHG+XSHE") # None — unlimited band mr.rule_at("stamp_duty_sell", "2005-01-01") # KeyError — no defaults, ever mr.citation() # 'rules: marina-rules@ sha256:<16 hex>'
mr.coverage("XSHE", "chinext", ["price_limit_pct"], "2019-01-01", "2026-10-19")
Dates are ISO YYYY-MM-DD strings or date / datetime objects (a timestamp such as 2020-08-23 09:30:00 counts as its day). Any other spelling — 20200823, 2020/8/23, an integer — raises ValueError and names the ISO form. It is refused rather than parsed because record intervals are compared as ISO text: read as given, 20200102 would select the rule of a later period.
python -m marina_rules.diff <old> <new> # in a clone: what changed, and what must be re-run; git tags or data directories
A rule is answered only under the name it is recorded with, for a scope that exists. Look the names up instead of guessing them — from Python or from the command line (marina-rules and python -m marina_rules are the same program):
mr.scopes() # scope → description, and the context it requires ("hk" / "us" for those registries)
mr.rules_for("cffex_if", "CCFX") # {'margin_ratio': [[from, to], …], 'price_limit_pct_of_prev_settlement': […], …} mr.statutory_fee_floor(86420.00, "sell", "2023-08-28", "XSHG") # 44.0742 — stamp duty + transfer fee of one fill mr.statutory_fee_components(86420.00, "sell", "2023-08-28", "XSHG") # the same, per rule, with record ids mr.skill_text() # the usage notes (SKILL.md) shipped inside the package
marina-rules # lists the subcommands
marina-rules scopes # add hk or us for those registries marina-rules rules cffex_if CCFX # rule names of one scope, first / last date (--intervals for all) marina-rules query price_limit_pct 2024-06-14 st_main XSHE --context board=main_board,st_status=true marina-rules fees 86420 sell 2023-08-28 XSHG # components, record ids and their sum marina-rules skill # the usage notes
When a lookup finds nothing, the refusal says what does exist: a KeyError message names the rules the scope has (or the intervals the rule has), and a decision from resolve() carries the same as alternatives (scope_rules, similar_rules, rule_intervals, similar_scopes). Names only, never a value — a similar name is a different rule (price_limit_pct is a fraction of the previous close; futures scopes carry price_limit_pct_of_prev_settlement), so read its definition and ask again. tick_size falls back to the stock family for mainland securities scopes only: a futures, Hong Kong or US scope asked for tick_size is refused.
coverage() answers "can Marina serve every (rule, day) in this window for this scope?" — complete, partial (with the exact gaps), or unsupported. It also tells you what you must already know about each security to select the scope legitimately (required_context): Marina holds rules, never a security's ST or listing history, and it will not guess them for you. Gaps carry known_gap_ids when they match data/cn/known_gaps.yaml (Hong Kong: data/hk/known_gaps.yaml; US: data/us/known_gaps.yaml) — the list of things Marina knows it does not cover (pre-2006 sessions and convertibles, the 2013 T+0 switch for bond/money/gold ETFs…), each with a reason and a status, so "unsupported" can be cited rather than worked around. Agents: read SKILL.md.
The data is plain YAML under data/. You do not need the Python package; read the files from any language.
The same questions can be put to the dataset by an AI assistant through the Model Context Protocol, without writing code. The server runs locally over stdio.
pip install "marina-rules[mcp]" # adds the MCP Python SDK; the server needs Python 3.10+, the rest of the package 3.9+
marina-rules-mcp # the same server: marina-rules mcp, python -m marina_rules.mcp_server
Add it to the MCP client's configuration (most clients read this mcpServers shape; where the file lives differs per client). If the client does not start in the environment where the package is installed, give the full path to marina-rules-mcp.
{
"mcpServers": { "marina-rules": {"command": "marina-rules-mcp"} } }
| tool | answers |
|---|---|
resolve | one rule on one trading day for one scope: the decision of resolve(), acted on only when status is DETERMINED |
limit_price | limit-up / limit-down price from the previous close; unlimited: true when no daily limit applied |
statutory_fees | stamp duty and transfer fee of one A-share stock fill, per component and summed (commission not included) |
coverage | whether every (rule, day) of a backtest window can be answered for a scope, with the gaps |
list_scopes | the scopes of cn, hk or us and the context each requires |
list_rules | the rule names a scope holds, with their first and last dates |
check_fills | the marina-check checks on up to 500 fills passed inline as JSON (not a file path) |
citation | the citation line and version of the dataset |
Every answer carries citation. Arguments the library refuses (a date not written YYYY-MM-DD, an unknown side) and questions with no record in force come back as tool errors whose text says what to change or what is missing; no value is filled in. The usage notes (SKILL.md) are offered as the resource marina-rules://skill.
What it does not do: it is read-only and deterministic, uses no network, and reads no file but the dataset shipped in the package. Like the package, it holds rules only — no prices, ST or suspension lists, constituents or trading calendar; a security's board, ST status and listing day are the caller's to supply.
<!-- mcp-name: