com.twmarketdata/tw-market-data
REMOTE · MCP.TWMARKETDATA.COM · SCANNED AUG 3
Taiwan stock market data (TWMD): official-source, point-in-time-safe datasets via read-only tools.
Available components
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 →
Endpoint Security89
- 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 offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 746 tokens (~186/item across 4 items; 4 tools + 0 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 Management3
- Stability observed for 1 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.twmarketdata.com
claude mcp add --transport http com-twmarketdata-tw-market-data https://mcp.twmarketdata.com/mcp
[mcp_servers.com-twmarketdata-tw-market-data] url = "https://mcp.twmarketdata.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-twmarketdata-tw-market-data": {
"type": "remote",
"url": "https://mcp.twmarketdata.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-twmarketdata-tw-market-data --url https://mcp.twmarketdata.com/mcp --transport streamable-http
mcp_servers:
com-twmarketdata-tw-market-data:
url: "https://mcp.twmarketdata.com/mcp" {
"mcpServers": {
"com-twmarketdata-tw-market-data": {
"type": "http",
"url": "https://mcp.twmarketdata.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +47
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 0 functional
- 2 Aug 26 +1
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- 31 Jul 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
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- HSTS header: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 28 Jul 26 0
- Transport: unverified → fail ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- 27 Jul 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 14
First indexed and scored.
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 3 Aug 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=WE1,O=Google Trust Services,C=US | 15 Jul 2026 | 13 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | d5ce25dd1b36376613196036af007835 |
| SANs: mcp.twmarketdata.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.twmarketdata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| twmarketdata.com. | absent | 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://eager-opera-76-staging.authkit.app |
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 | 301 | 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.
describe_dataset ~85
FULL semantics of one dataset: grain (what a row is), field meanings+units, ★TIME-CORRECTNESS rules (knowledge_time_field / point_in_time_safe — read before backtesting), relations for cross-table reasoning, agent_hints (when to use), quant_use (which factors). Args: dataset_id.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| adjustments | — | — | — |
| agent_hints | — | — | — |
| category | — | — | — |
| coverage | — | — | — |
| error | — | — | — |
| grain | — | — | — |
| hint | — | — | — |
| id | — | — | — |
| key_fields | — | — | — |
| name_zh | — | — | — |
| quant_use | — | — | — |
| relations | — | — | — |
| temporal | — | — | — |
| tier | — | — | — |
No examples provided.
find_related ~98
Traverse the knowledge graph for cross-table / supply-chain reasoning. - dataset_id: returns join-able datasets (+why) to plan multi-table analysis. - ticker: returns its industry value-chain node + peers in the same node (supply-chain reasoning). Args: dataset_id (e.g. 'equity_daily_prices') and/or ticker (e.g. '2330').
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | — | — | — |
| ticker | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| chain_error | — | — | — |
| dataset_relations | — | — | — |
| error | — | — | — |
| note | — | — | — |
| peers_in_node | — | — | — |
| ticker | — | — | — |
| value_chain_nodes | — | — | — |
No examples provided.
list_datasets ~147
List available Taiwan-market datasets (discovery entry point). Returns id / 中文名 / category / tier / one-line description for each. Use this first to find the right data. Args: category: optional, e.g. 'chip'(籌碼) 'fundamental'(基本面) 'price'(行情) 'macro'(總經) 'relation'(關聯/產業鏈) 'derivatives'(期權) 'event'(事件) 'rag_text'(文本). tier: optional minimum plan: 'free' 'starter' 'pro' 'max' 'developer' 'enterprise'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | — | — | — |
| tier | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| count | — | — | — |
| datasets | — | — | — |
No examples provided.
query_dataset ~253
Query rows with built-in look-ahead protection. ★ POINT-IN-TIME: pass `as_of` (YYYY-MM-DD) for backtesting/agent-learning. For non-point-in-time-safe datasets (fundamentals, monthly_revenue, dividend_policy…) rows are filtered by DISCLOSURE date <= as_of, so the agent only sees what was public at that moment. Omit as_of only for present-day lookups (warned). Args: dataset_id: see list_datasets. tickers: e.g. ['2330','2317']. start/end: 'YYYY-MM-DD' range. as_of: knowledge-time cutoff 'YYYY-MM-DD' (use for backtests). limit: <=5000. Returns: {meta:{table,coverage,row_count,as_of_applied,point_in_time_safe,warnings}, data:[...]} Example: query_dataset('fundamental_income', tickers=['2330'], as_of='2023-06-30')
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | — | — | — |
| dataset_id | string | yes | — |
| end | — | — | — |
| limit | integer | — | — |
| start | — | — | — |
| tickers | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| blocked | — | — | — |
| data | — | — | — |
| error | — | — | — |
| hint | — | — | — |
| message | — | — | — |
| meta | — | — | — |
| status | — | — | — |
No examples provided.