Skip to content

MCP servers › io.github.open-winmale › wmshare

MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19

wmshare MCP server

Registry name io.github.open-winmale/wmshare

by open-winmale · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗

Python SDK MCP server: offline catalog + 2,983 precomputed A-share/HK/US metrics for AI agents. — the publisher's description

8 of 8 record checks metversion 2.4.2PythonBSD-3-Clausestandard input/output

Summary

io.github.open-winmale/wmshare is a local MCP server listed in the official MCP registry at version 2.4.2, under the namespace of the GitHub account open-winmale. Its linked repository, github.com/open-winmale/wmshare, belongs to the same GitHub account.

Record checks

8 of 8 record checks met · 1 does not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #633 of 20,610 packages by monthly downloads
  • #2,018 of 28,859 repositories by GitHub stars, tied with 48 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
PyPI · listed version current
License
BSD-3-Clause
Dependencies
no known high or critical advisories
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
2.4.2, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-10 (earliest version still in the registry; older removed versions would be earlier)
Version history
22 versions listed, 2026-11-10 to 2026-11-19; 22 in the 90 days before the 2026-11-19 snapshot.
Most recent 12 versions
  • 2.4.2 · 2026-11-19
  • 2.4.1 · 2026-11-19
  • 2.4.0 · 2026-11-19
  • 2.3.1 · 2026-11-19
  • 2.3.0 · 2026-11-19
  • 2.2.1 · 2026-11-18
  • 2.2.0 · 2026-11-18
  • 2.1.0 · 2026-11-18
  • 2.0.1 · 2026-11-17
  • 2.0.0 · 2026-11-17
  • 1.21.0 · 2026-11-16
  • 1.19.1 · 2026-11-13
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 2.2.1 (published 2026-11-18) → 2.4.2 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher’s GitHub release note for v2.4.2, published 2026-11-19.

Read the release note (the publisher’s text, shown as plain text)
### Fixed
- **英文 Quickstart 计费模型写反**(`docs/QUICKSTART_EN.md`):原文「Requests are
  billed **per request**, not per row — which is why batching matters」与 EC 的真实
  计费口径相反——EC 按服务端物化行计,批量只省请求数与调度、**不省 EC**(见
  `docs/LIMITS.md` §4)。英文用户照此跑全市场会严重超额。改为双计费口径说明
  (限流按请求 / 计费按 EC 行),并补 `cli.cost_estimate` 先估后取入口。同文件
  修正 2,752→2,983 指标码、132→152 核心接口、快照日期、示例输出值与示例数。
- **`demo_client()` 的同签名承诺不成立**:DemoClient 缺 8 个命名空间
  (`cbond`/`etf`/`intl`/`segments`/`filings`/`forecast`/`workout`/`estimates`)
  与多个方法,README 推荐的 `cli.notice.has_buyback(...)` 在 demo 上直接
  `AttributeError`——等于「假装没有这个能力」。新增 `_UnsupportedNamespace` 垫片:
  属性存在且可调用,调用即抛 `UsageError(code="demo_unsupported")`,并按 live
  门面挂真实 `__signature__`;dunder 名仍走 `AttributeError`。
- **单位口径文档自相矛盾**:README/GUIDE 称「全库返回前做量级校验」,而
  `docs/INDICATORS.md` 明说只有精选 78 码带守护(函数级 66/317 ≈ 20.8%)。
  两处表述已对齐;同时把文档示例里 `up_pct` 的 80.3 / 9.5 改为小数
  (0.803 / 0.095),与 2.0「`*_pct` 一律小数」契约一致——此前测试 FakeClient
  直接返回百分数,把错误示例焊死成绿色。
- **`docs/ERRORS.md` 处理范式示例无法运行**:`from wmshare import QuotaError`
  报 `ImportError`(`QuotaError` 未从包根导出),而 `test_errors_doc_in_sync`
  只比对「生成器输出 == 文档」,把错行硬编码进生成器后门禁永远绿。已导出
  `QuotaError`(`LimitError` 子类,纯增量)、示例补 `import time`。
- **`estimate_cost` 严重低估多票成本**:`valuation.daily_basic` 分支忽略
  `syms` 票数,200 票时报的是单票价(低估一个数量级以上)。按 2026-11-19 live
  实测 9 个点(1/5/10/30/50 票 × 跨度 1/18/90 自然日)拟合为
  `150 + 票数 × (230 + 20 × 跨度)`,全部落点误差 <12%;`syms>1` 时 note
  明示「EC 按票计价,批量不省算力」。
- 对外计数与日期漂移:`server.json` 描述 2,752→2,983(MCP Registry 机器可读
  描述)、`SKILL.md` 5,691→5,375 家与 12→11 次请求、`GUIDE.md` 空参捷径阈值
  ≥4,000→≥2,000 票与 311→317 函数、README 12→11 次请求、examples 的
  `wmshare[dataframe]` 死引用(2.0 起 pandas 为核心依赖)、README/examples 的
  「18 个示例全部支持离线」实际为 3 纯离线 + 14 `--demo` + 1 需凭证。

### Changed
- **门禁扫描面扩围**:`test_docs_no_stale_counts` 纳入 `QUICKSTART_EN`、
  `METRIC_ADAPTER`、`examples/README`、`server.json` 并补英文计数 pattern;
  扩围后立刻抓出 3 处此前漏掉的真实漂移。
  `test_demo_signatures_cover_live_facade_params` 不再对 demo 缺失方法
  `continue` 静默跳过(缺失即失败),新增
  `test_demo_unbacked_calls_raise_demo_unsupported`、
  `test_quickstart_en_matches_runtime`、`test_pct_example_values_are_decimals`、
  `test_errors_doc_snippet_imports_resolve` 四条防回归门禁。
- `docs/PROMOTION.md` 迁出仓库(→ 工作区 `../promo/`):推广执行手册属方案/流程
  类文档,`CONTRIBUTING.md` 明确要求不入库。
- **release 流水线新增前置质量门禁**(`.github/workflows/release.yml`):
  job 链改为 `gates → release → publish-pypi`,PyPI 上传前跑与 `ci.yml` 同款的
  离线门禁(leak / catalog / taxonomy / units / 版本互校 / 许可证 / 守卫覆盖率 /
  8 个生成物漂移 / mypy / pytest)。此前 release.yml 只做版本互校 + twine check,
  1.21.0 因此把指向已下线底层函数的门面直接发上 PyPI,次日才出补丁;发布件不可
  撤回,故门禁必须前置到流水线而非依赖人工记忆。

The release on GitHub

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the PyPI package names the runner "wmshare-mcp", not uvx.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
2.4.2
Latest stable
2.4.2
Status
current
Withdrawn
no

Source: pypi.org · 2026-11-19. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-19 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-1ddf41c8b6a84b1ee…
License
BSD-3-Clause

Source: the package registry · 2026-11-19.

Usage

Downloads
4,984 in the last month

Source: pypistats.org · 2026-11-19.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 2.4.2 on PyPIExists and can be installedmatchesPyPI · 2026-11-19
Repository github.com/open-winmale/wmshareOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.open-winmale
GitHub owner
an organization (open-winmale)
Repository
github.com/open-winmale/wmshare
Stars
24
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 8 record checks met · 1 does not apply

  • #633 of 20,610 packages by monthly downloads
  • #2,018 of 28,859 repositories by GitHub stars, tied with 48 others
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierBSD-3-Clause
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.open-winmale/wmshare

Answered from the data above

Who publishes io.github.open-winmale/wmshare?

The registry ties the namespace io.github.open-winmale to the GitHub account open-winmale; only its owner can publish under it. Its linked repository, github.com/open-winmale/wmshare, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.open-winmale/wmshare safe to install?

We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.open-winmale/wmshare been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.open-winmale/wmshare publish a security policy?

Yes: its repository has a public security policy (github.com/open-winmale/wmshare/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 2.4.2, the latest stable release on PyPI.

Where is the source code of io.github.open-winmale/wmshare?

In github.com/open-winmale/wmshare, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
registry · 2026-11-19
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
package registry · 2026-11-19
Integrity hash
declared (sha256)
package registry · 2026-11-19
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-11-19
Popularity
4,984 downloads a month
package registry · 2026-11-19
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 10–99
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
your machine
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.open-winmale/wmshare: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.open-winmale/wmshare

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 8 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.open-winmale/wmshare)](https://protocolprobe.com/mcp/servers/io.github.open-winmale/wmshare)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology