com.twmarketdata/tw-market-data
REMOTE · MCP.TWMARKETDATA.COM
Taiwan stock market data (TWMD): official-source, point-in-time-safe datasets via read-only tools.
Available components
Last scanned (12 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 11769 tokens (~250/item across 47 items; 41 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- Tool “search_filings” rewrote its description, which is the text the model reads security
- 7 Oct 26 0
- Tool “screen” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Tool “run_backtest” rewrote its description, which is the text the model reads security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Tool “query_dataset” rewrote its description, which is the text the model reads security
- 22 Sept 26 0
- Tool “run_backtest” rewrote its description, which is the text the model reads security
- “run_backtest” added an optional parameter “costs” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.twmarketdata.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.twmarketdata.com | CN=YR1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 4096 | SHA256-RSA | 63991047ad76a51d017a4caf350ee9a5b15 |
| SANs: mcp.twmarketdata.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.twmarketdata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| twmarketdata.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.twmarketdata.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.twmarketdata.com/.well-known/oauth-protected-resource" Protected resource metadata
| Document | https://mcp.twmarketdata.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.twmarketdata.com/mcp |
| Authorisation server | https://flourishing-dinosaur-46.authkit.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.twmarketdata.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.twmarketdata.com/mcp | HTTPS enforced | 302 | https://mcp.twmarketdata.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search_filings Search filings and announcements ~675
Semantic search over MOPS filings and announcements — ⚠️ NOT YET AVAILABLE (語意檢索尚未提供/建置中). ★ STATUS, READ FIRST: the semantic index has not been built. Every call currently returns NO rows, with `corpus.index_is_empty: true` and `corpus.service_status: "not_yet_available"`. Tell the user this capability is not available yet. Do NOT present it as a working feature, and do NOT read the empty result as "the company disclosed nothing" — it is a service state, not a fact about any company. Once built, it matches on MEANING rather than keywords. The declared corpus is MOPS 重大訊息 subject lines plus a small MOPS full-text set; financial-statement notes do not exist in this database and company news is refused — `corpus` in every response says exactly what is indexed. ★ POINT-IN-TIME: pass `as_of` (YYYY-MM-DD). Chunks are filtered `published_at <= as_of` in SQL BEFORE ranking, so a backtest cannot retrieve a filing that did not exist yet. `meta.as_of_applied` echoes the cutoff that actually ran — check it. **Without `as_of` the results include the most recent filings and are look-ahead UNSAFE for backtesting**; the response says so in `meta.warnings`. ★ REFERENCE CONTEXT, NOT AUTHORITY. Every hit carries `source`, `source_tier` ("official" = MOPS/exchange, "third_party" = press) and a `url`. Read the chunk and judge it yourself; the ranking is similarity, not importance, and similarity is not evidence. **Nothing here is investment advice** (`not_investment_advice: true`). ★ A ticker you asked about that returns nothing appears in `coverage.missing` with a reason. That means NOTHING IS INDEXED for it under those filters — it does NOT mean the company disclosed nothing. Do not fill the gap. Args: query: what to look for, in Chinese or English (e.g. '匯率風險', 'CoWoS capacity'). tickers: restrict to these codes, e.g. ['2330','2317']. doc_type: 'mops_major_event' or 'mops_a…
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| doc_type | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| source_tier | – | – | – |
| tickers | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_price_alert Set a price alert ~255
Leave a standing instruction: tell me when this symbol crosses this price. The alert OUTLIVES this conversation. It is evaluated against official daily closes by a resident agent and delivered to your realtime stream and to any webhook endpoints you have registered — signed, retried, and de-duplicated so one crossing is one notification. This is a NOTIFICATION, not an order. Nothing in TWMD can place a trade. Args: rule_id: your name for this alert. Re-using one UPDATES it rather than adding a second. symbol: the Taiwan ticker, e.g. "2330". direction: "below" or "above". threshold: the price level, in TWD. label: optional human-readable note carried on the alert. edge_triggered: True (default) fires on the CROSSING only — one long slump does not notify you every day. False fires on every bar that is past the level.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | – |
| edge_triggered | boolean | – | – |
| label | – | – | – |
| rule_id | string | yes | – |
| symbol | string | yes | – |
| threshold | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| blocked | – | – | – |
| deleted | – | – | – |
| delivery | – | – | – |
| error | – | – | – |
| hint | – | – | – |
| not_investment_advice | – | – | – |
| reason | – | – | – |
| rule | – | – | – |
| rule_id | – | – | – |
No examples provided.
supply_chain_read Read the supply chain ~279
供應鏈與同業:產業鏈位置、同業分組、轉投資、外銷訂單 vs 營收。 ★ 事實整理,不是投資建議、不是預測。輸出帶 `does_not_prove`。 ★ ⚠️ `company_peer_groups` 無日期欄:指定過去的 `as_of` 時,回的是**現況**分組, `pit_notes` 會標「非當時分類」。 ★ ⚠️ 質化的客戶/供應商關係與分部營收在年報附註,那條來源**尚未建置** —— 固定列在 `cannot_see`(status=no_loader),不是這次查失敗。 ★ Args:`ticker`(例如 "2330")、`as_of`(選填)。 ★ Returns:誠實信封;外銷訂單與營收的背離會 listed in `concerns`。 ★ PRECONDITIONS:自己取數;requires 一個已識別的 session。 ★ SIDE EFFECTS:read-only,does not 寫入。
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
try_sample Try a free sample (no key) ~345
Hand an unregistered caller a short taste of an open dataset, plus where to unlock the rest. ★ WHAT AN ACCOUNTLESS CALLER GETS INSTEAD OF A BARE REFUSAL. Somebody arriving through a chat connector with no plan would otherwise meet a flat rejection, which the host model relays as "this service turned you down". ★ WHAT IS ACTUALLY FREE, STATED CONCRETELY. The reference resources read with no key at all, and the five sample tickers (2330, 2317, 2454, 0050, 2603) answer through `query_dataset` with no plan. Querying beyond those over MCP starts at the Pro plan. ★ OPEN DATASETS YIELD A FEW MARKED ROWS; PAID ONES YIELD NONE. For a paid dataset the row list is not even consulted, so no figure can escape through this path regardless of what the caller passes in. `rows_withheld` states how many were held back, because a taste that does not say it is a taste reads as the whole thing. ★ NOT `query_dataset`. That one serves entitled callers in full. This exists only for the moment somebody hits the edge of what they are entitled to. ⚠️ Withdrawn datasets stay refused here too — a licence ruling is not a tier, so no amount of signing up unlocks them. Args: dataset, keyless_eligible, rows.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| keyless_eligible | boolean | – | – |
| rows | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the com.twmarketdata/tw-market-data MCP server?
com.twmarketdata/tw-market-data is a hosted endpoint at https://mcp.twmarketdata.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.twmarketdata.com
claude mcp add --transport http com-twmarketdata-tw-market-data 'https://mcp.twmarketdata.com/mcp'
What is the com.twmarketdata/tw-market-data MCP server?
com.twmarketdata/tw-market-data is an MCP server listed in the public MCP registry as com.twmarketdata/tw-market-data. Taiwan stock market data (TWMD): official-source, point-in-time-safe datasets via read-only tools. This page covers its hosted endpoint (https://mcp.twmarketdata.com/mcp).
Is the com.twmarketdata/tw-market-data MCP server safe to use?
com.twmarketdata/tw-market-data scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.twmarketdata/tw-market-data MCP server expose?
com.twmarketdata/tw-market-data exposes 41 tools: list_datasets, describe_dataset, query_dataset, find_related, search_filings, and 36 more. Their descriptions and schemas cost roughly 11,424 tokens of context every time the server is loaded.
Does the com.twmarketdata/tw-market-data MCP server require authentication?
Yes. com.twmarketdata/tw-market-data asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.twmarketdata/tw-market-data MCP server still maintained?
com.twmarketdata/tw-market-data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.twmarketdata/tw-market-data MCP server?
VerifyMCP ran 13 checks on com.twmarketdata/tw-market-data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.