Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

China Futures Clock

REMOTE · MCP.FUTURESCLOCK.COM

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

72 Trust /100

Last scanned (4 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 423 tokens (~70/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Changelog

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

    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.

  • 3 Nov 26 +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.

  • 2 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 70

    First indexed and scored.

Diagnostics

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.futuresclock.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=futuresclock.com CN=WE1,O=Google Trust Services,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA256 32ae9e037ad340dc13d6c2904751e3f3
SANs: futuresclock.com, mcp.futuresclock.com, *.mcp.futuresclock.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

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.futuresclock.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
futuresclock.com. present 2371 13 Verified
mcp.futuresclock.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.futuresclock.com/mcp Verified 200
http (plaintext) http://mcp.futuresclock.com/mcp HTTPS enforced 301 https://mcp.futuresclock.com/mcp
MCP tools · 6 exposed · ~423 tokens

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 →

Tool Tokens
contract_expiry ~70

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.

NameTypeReqDescription
monthstring––
productstringyes–

No output schema declared.

No examples provided.

next_closure ~50

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.

NameTypeReqDescription
exchangestringyes–

No output schema declared.

No examples provided.

recent_notices ~82

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.

NameTypeReqDescription
daysinteger––
exchangestring––
langstring––
topicstring––

No output schema declared.

No examples provided.

recent_rule_changes ~84

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.

NameTypeReqDescription
daysinteger––
exchangestring––
productstring––
topicstring––

No output schema declared.

No examples provided.

trading_day ~69

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.

NameTypeReqDescription
datestring––
exchangestringyes–

No output schema declared.

No examples provided.

trading_hours ~68

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.

NameTypeReqDescription
datestring––
productstringyes–

No output schema declared.

No examples provided.

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.

remote · mcp.futuresclock.com

# add to Claude Code
claude mcp add --transport http com-futuresclock-china-futures 'https://mcp.futuresclock.com/mcp'
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.