Back to Browse

Tw Market Live Data Intelligence MCP Server

Developer ToolsUse Caution4.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

Local-first Taiwan market evidence for AI agents: Watchlists, governed MCP, audited execute-once.

About

Local-first Taiwan market evidence for AI agents: Watchlists, governed MCP, audited execute-once.

Security Report

4.8
Use Caution4.8High Risk

This is a well-structured MCP server for Taiwan market data intelligence with appropriate security controls. The code demonstrates careful design around data governance, schema validation, and safety boundaries. No critical vulnerabilities detected; permissions align with the stated purpose of providing market data with identity-aware, bounded execution workflows. Supply chain analysis found 6 known vulnerabilities in dependencies (0 critical, 1 high severity).

3 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Install command not verified. See the repository for install instructions.

View repository

Documentation

View on GitHub

From the project's GitHub README.

TW-Market Live Data Intelligence

English | 繁體中文

Stable v1.5.1 Windows 11 x64 Python 3.13 MCP six tools License MIT

Local-first, governed Taiwan-market evidence infrastructure for human operators and AI agents — validate first, preview bounded work, then explicitly authorize one execution only when the current capability and route permit it.

Architecture at a glance

flowchart LR
    H[Human / Operator] --> W[Unified Workbench]
    A[AI Agent] --> M[Six-tool MCP]
    W --> R[Unified Runtime]
    M --> R
    R --> V[Validate + Identity]
    V --> P[Preview + Route Bounds]
    P --> X[Explicit Authorization]
    X --> E[Execute Once]
    E --> S[Governed Official / Approved Sources]
    S --> O[Result + Audit + AI Handoff]
    L[Persistent Watchlists] --> W

Current stable release

TW-Market v1.5.1 is the latest stable GitHub Release, published on 2026-11-04 (23:57 Asia/Taipei). ProductVersion: 1.5.1.

The v1.5.1 tag/source and six published assets remain immutable under release governance. Later documentation-only commits on main are not new v1.5.1 release bytes. GitHub Immutable Releases platform enforcement is not asserted. Previous v1.5.0 remains a valid frozen historical release.

Why upgrade from v1.5.0? Windows Native operator experience

The main v1.5.1 improvement is a guided, operator-first Windows workflow verified across RMA-0 through RMA-11 — not simply an internal patch.

  • Open the package-root Launch-TW-Market.cmd instead of starting with Python, PowerShell, source folders or manual service commands. The graphical first-run setup checks the external Python 3.13 x64 prerequisite.
  • Set up once, operate daily: status cards for Local Runtime, Workbench, Security Master and Local MCP; explicit Start, Stop, Refresh, Diagnose and Open Workbench controls.
  • Manage Security Master visibly: Install/Update, confirmation before official-source acquisition, clear restart guidance and a verified-TLS compatibility retry only when justified by current source evidence.
  • Build requests without editing raw JSON: Workbench Request Builder, Compose, Validate and Preview; explain blocking conditions and offer bounded recovery guidance before authorization.
  • Know exactly when data will be fetched: explicit Authorize, separate network confirmation, and Execute Once; then inspect Result/Audit and export an AI-ready Mode C handoff. Advanced technical payloads remain available but no longer dominate the primary journey.

See the complete Windows Native v1.5.1 guided workflow and RMA-0–11 evidence.

This is not a zero-dependency installer: Python 3.13 x64 is still required; Setup does not install Python or fetch market data; Security Master acquisition and any live evidence execution require explicit operator authorization. No scheduler, automated trading or realtime data guarantee is included.

Choose your path

PathBest forStart here
Windows Native ZIPNormal local operator / Workbench useDownload v1.5.1 Native ZIP
Windows MCPBAI / MCP clientDownload v1.5.1 MCPB
Source checkoutDeveloper / contributorSource/developer path

For a 60-second orientation and first-run sequence, use the Operator Quick Start. The Native ZIP is the recommended operator path; source checkout is not the default installation path for every user.

For developer-only source checkout, python scripts/run_unified_workbench.py and python scripts/run_unified_market_evidence_mcp.py remain explicit advanced entry points; neither replaces the built Native bundle-root Launcher.

What TW-Market is

TW-Market is a governed evidence and research workbench for Taiwan-market data. It gives a human operator or AI agent a deterministic path from target identity and capability validation to bounded source acquisition, canonical Result/Audit materialization, citations, and an AI-ready handoff.

It is intentionally not a broker, autonomous trader, portfolio system, general-purpose crawler, or realtime-price guarantee.

Core product characteristics:

  • Local-first: installation state, Security Master, Watchlists, evidence, and audit artifacts remain under explicit local control.
  • Identity-aware: Taiwan cash instruments use ISIN as durable identity and MARKET:CODE as listing/routing identity.
  • Preview before execute: validation and preview do not authorize network acquisition; execution is explicit, bounded, and auditable.
  • Persistent Watchlists are supported: installation-local Watchlists use immutable revisions, optimistic concurrency, and explicit preview/commit mutation.
  • Evidence, not conclusions: source authority, timing/currentness, missingness, caveats, and citations remain visible to downstream humans and AI.

Governed workflow

A typical 2330 flow is:

  1. Create or select an installation-local Watchlist and add 2330.
  2. Compose a Unified Market Evidence Request and validate identity/capability.
  3. Preview the exact planned operation and its route boundary.
  4. Explicitly authorize one bounded execution only if the preview is executable.
  5. Read the canonical Result and Audit Package, or export the AI-ready handoff.

Unified Request v3 is preferred. Request v1/v2 remain supported compatibility contracts; historical supported Result/Audit packages remain readable without rewriting their canonical bytes or provenance.

The Unified MCP surface remains exactly six governed tools:

market_describe_capabilities, market_validate_request, market_preview_request, market_read_result, market_export_ai_handoff, and market_fetch_evidence.

See the AI usage guide and V1 historical public contracts for the current request/result/handoff semantics and compatibility boundary.

Deterministic Unified Workbench overview

Current evidence capabilities

Current governed product scope includes:

  • installation-local Taiwan Market Identity Service and persistent Watchlists;
  • official material-disclosure and monthly-revenue evidence for eligible TWSE/TPEx company common shares;
  • selected bounded market-state, index-futures, institutional-flow, corporate-action, and recent-performance context where current Catalog and Routing authority make the requested market/target executable;
  • canonical Result/Audit lineage, citations, timing/currentness semantics, and AI-ready Markdown handoff.

Capability support is not the same as route executability. A known instrument, schema, or capability does not by itself authorize source acquisition. Always validate and preview against the current Catalog and selected Routing.

Research evidence is intentionally bounded. It does not imply arbitrary history, realtime disclosures, a full-market scanner, financial_summary, investment advice, or trading signals.

Safety boundary

There is no automatic polling, scheduler, startup market fetch, Watchlist-driven automatic execution, trading, or order routing. There is also no silent source fallback or model-selected executor/URL. Missing evidence is not converted to zero, and execution success is not presented as a realtime guarantee.

Source/developer quick start

Use the primary source first-run sequence for dependencies, offline lifecycle initialization, Local Service, Workbench and MCP preflight. Initialization and Security Master activation are separate: identity-dependent operations fail closed while identity is unavailable, but health/UI/capability inspection can start after installation initialization. The source MCP stdio adapter requires the running loopback Local Service.

The release ZIP/MCPB installation paths are documented separately; keep those operator instructions distinct from this source/developer path.

MCP distribution and registry boundary

The published GitHub v1.5.1 Release includes the Windows MCPB and its SHA-256 sidecar. This local stdio package exposes exactly six governed tools.

The separate official MCP Registry identity, io.github.SmartyJohnway/tw-market-live-data-intelligence, was checked through the official live Registry API on 2026-11-05: its Latest active version is 1.0.0. GitHub v1.5.1 publication does not imply Registry v1.5.1 publication; updating server.json requires separate authorization.

See MCP distribution for installation and Unified MCP Reference for the six tools.

Docker is a validated local linux/amd64 build/acceptance and provenance surface only. No Docker registry image is published for v1.5.1.

Documentation

Operator and product docs:

Engineering/governance front doors:

Historical engineering and acceptance records remain available for audit and compatibility, but they are not a second current-product contract. Start with Project History or the Engineering history / protocol archive.

Release history and provenance

  • v1.5.1 — current stable GitHub Release (2026-11-04), six verified assets.
  • v1.5.0 — prior frozen stable GitHub Release (2026-10-28).
  • v1.0.0 — historical GitHub stable release, and current MCP Registry package version (verified in the official Registry on 2026-11-05).
  • v1.0.0-rc.1 — historical prerelease.
  • v0.1.0 — earlier GitHub stable release.

The published v1.5.1 assets include Native ZIP/checksum, MCPB/checksum, first-party SBOM and typed publication manifest. SHA-256, provenance and SBOM prove integrity/traceability, not cryptographic publisher signatures; signing authority remains NOT_ESTABLISHED. See the post-publication record for exact SHA-256 values and preserved non-blocking diagnostic results.

Contributing and security

Read CONTRIBUTING.md before opening a pull request. Report security concerns using SECURITY.md. Never commit credentials, tokens, cookies, or private market payloads.

License

See LICENSE.

Reviews

No reviews yet

Be the first to review this server!