# China Futures Clock (remote · mcp.futuresclock.com)

China futures trading days, session hours, contract expiries and exchange rule changes.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.futuresclock.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-futuresclock-china-futures/mcp.md), [page](https://verifymcp.io/servers/com-futuresclock-china-futures/mcp)

## Channel facts

- Endpoint: `https://mcp.futuresclock.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 423 tokens (~70/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the China Futures Clock MCP server?

China Futures Clock is a hosted endpoint at https://mcp.futuresclock.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.

### Claude

```bash
claude mcp add --transport http com-futuresclock-china-futures 'https://mcp.futuresclock.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-futuresclock-china-futures": {
      "url": "https://mcp.futuresclock.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-futuresclock-china-futures": {
      "type": "http",
      "url": "https://mcp.futuresclock.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-futuresclock-china-futures]
url = "https://mcp.futuresclock.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-futuresclock-china-futures": {
      "type": "remote",
      "url": "https://mcp.futuresclock.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-futuresclock-china-futures --url 'https://mcp.futuresclock.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-futuresclock-china-futures:
    url: "https://mcp.futuresclock.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-futuresclock-china-futures": {
      "Transport": "http",
      "Url": "https://mcp.futuresclock.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-futuresclock-china-futures -t streamable-http -u 'https://mcp.futuresclock.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-futuresclock-china-futures": {
      "type": "http",
      "url": "https://mcp.futuresclock.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 70)

First indexed and scored.

## MCP tools (6)

### `trading_day` (~69 tokens)

Exchange-local trading date and civil/incoming night attribution. Mainland China and the 24 MO scopes; SGX is equity/FX/rates, HKEX is cash equities. Outside published coverage is unknown. Official exchange notices take precedence.

Input parameters:

- `date` (string)
- `exchange` (string, required)

### `next_closure` (~50 tokens)

Next published exchange holiday or half-day from the fixed MO static calendar list; weekends alone are not holiday events. No extrapolation beyond coverage. Official exchange notices take precedence.

Input parameters:

- `exchange` (string, required)

### `trading_hours` (~68 tokens)

FC product session templates, explicit day-offset units and special hours under data contract v0.1. Date selects the exchange-local schedule; no real-time market status or prices. Missing prerequisites are unknown. Official exchange notices take precedence.

Input parameters:

- `date` (string)
- `product` (string, required)

### `contract_expiry` (~70 tokens)

Published FC last-trading/first-notice dates for a product and optional YYYYMM delivery month (default next published month). Never runs an expiry engine; unpublished months are unknown with a product-page link. Official exchange notices take precedence.

Input parameters:

- `month` (string)
- `product` (string, required)

### `recent_rule_changes` (~84 tokens)

CEC published rule changes: margin, price limits, position/opening limits, fees, delivery and listing. Requested window at most 90 days; reports actual available window, never current parameter history. Official Chinese exchange notices take precedence.

Input parameters:

- `days` (integer)
- `exchange` (string)
- `product` (string)
- `topic` (string)

### `recent_notices` (~82 tokens)

CEC published notice records in Chinese or available English summaries; at most 30 days. Falls back to Chinese when English is unavailable, without translation. Published records are not verified current rules. Official Chinese exchange notices take precedence.

Input parameters:

- `days` (integer)
- `exchange` (string)
- `lang` (string)
- `topic` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-futuresclock-china-futures/mcp#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70

## Common questions

### What is the China Futures Clock MCP server?

China Futures Clock is an MCP server listed in the public MCP registry as com.futuresclock/china-futures. China futures trading days, session hours, contract expiries and exchange rule changes. This page covers its hosted endpoint (https://mcp.futuresclock.com/mcp).

### Is the China Futures Clock MCP server safe to use?

China Futures Clock scores 72 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 China Futures Clock MCP server expose?

China Futures Clock exposes 6 tools: trading_day, next_closure, trading_hours, contract_expiry, recent_rule_changes, recent_notices. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.

### Does the China Futures Clock MCP server require authentication?

No. We connected to China Futures Clock without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the China Futures Clock MCP server still maintained?

China Futures Clock 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 China Futures Clock MCP server?

VerifyMCP ran 13 checks on China Futures Clock, 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.

## Links

- Remote endpoint: https://mcp.futuresclock.com/mcp
- Website: https://futuresclock.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-futuresclock-china-futures/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-futuresclock-china-futures/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-futuresclock-china-futures/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-futuresclock-china-futures/mcp