TradingCalendars
REMOTE · API.TRADINGCALENDARS.COM
Business days, T+N settlement dates and holidays for FX, banks, payments and exchanges.
Available components
Last scanned (1 hour ago)
Scores higher than 53% 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1360 tokens (~80/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “add_business_days” changed its title: Add business days (T+N date) cosmetic
- Tool “bank_holidays” changed its title: Bank holidays cosmetic
- Tool “business_days_between” changed its title: Business days between two dates cosmetic
- Tool “currency_non_clearing_days” changed its title: Currency settlement (non-clearing) days cosmetic
- Tool “fx_market_holidays” changed its title: FX market holidays cosmetic
- Tool “get_holidays” changed its title: Holidays for a calendar cosmetic
- Tool “get_weekends” changed its title: Weekend definitions cosmetic
- Tool “is_business_day” changed its title: Is it a business day? cosmetic
- Tool “list_calendars” changed its title: List calendars cosmetic
- Tool “list_currencies” changed its title: List currencies cosmetic
- Tool “list_exchanges” changed its title: List exchanges cosmetic
- Tool “list_financial_centres” changed its title: List financial centres cosmetic
- Tool “list_payment_systems” changed its title: List payment systems cosmetic
- Tool “market_status” changed its title: Market open/closed status cosmetic
- Tool “payment_system_holidays” changed its title: Payment system holidays cosmetic
- Tool “settlement_holidays” changed its title: Exchange settlement holidays cosmetic
- Tool “trading_holidays” changed its title: Exchange trading holidays cosmetic
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 60
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 5 Nov 2026 · Probed https://api.tradingcalendars.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tradingcalendars.com | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3f4c7757216a80570e4b0043a7ff16b2 |
| SANs: tradingcalendars.com, *.tradingcalendars.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 insecure
Validation of api.tradingcalendars.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tradingcalendars.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.tradingcalendars.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.tradingcalendars.com/mcp | HTTPS enforced | 301 | https://api.tradingcalendars.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 →
add_business_days Add business days (T+N date) ~185
Date that is N business days after (or before, with negative days) a start date: settlement and value dates (T+1 = 1, T+2 = 2), payment due dates, deadlines. days = 0 rolls a non-business start forward to the next business day. Lists every non-business day skipped and why. calendars: one or more calendar codes from list_calendars, e.g. ["USD.FX", "EUR.FX"] for a EUR/USD FX trade, ["XNYS.SETTLE"] for NYSE settlement, ["TARGET2.PAY"] for euro payments, ["GBLON.BANK"] for London banks. A date counts as a business day only when it is open in every calendar given. date defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | array | yes | – |
| date | – | – | – |
| days | integer | yes | – |
No output schema declared.
No examples provided.
bank_holidays Bank holidays ~60
Bank holidays for a financial centre (UN/LOCODE, e.g. USNYC): days retail and commercial banks are closed. start defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| financial_centre | string | yes | – |
| start | – | – | – |
No output schema declared.
No examples provided.
business_days_between Business days between two dates ~144
Number of business days between two dates (start counted, end not counted, like numpy.busday_count), with the non-business days in between and why. calendars: one or more calendar codes from list_calendars, e.g. ["USD.FX", "EUR.FX"] for a EUR/USD FX trade, ["XNYS.SETTLE"] for NYSE settlement, ["TARGET2.PAY"] for euro payments, ["GBLON.BANK"] for London banks. A date counts as a business day only when it is open in every calendar given.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | array | yes | – |
| end | string | yes | – |
| start | string | yes | – |
No output schema declared.
No examples provided.
currency_non_clearing_days Currency settlement (non-clearing) days ~65
Currency non-clearing days (ISO 4217, e.g. USD): days the currency cannot clear or settle. Use to validate FX value dates. start defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| end | – | – | – |
| start | – | – | – |
No output schema declared.
No examples provided.
fx_market_holidays FX market holidays ~60
FX market holidays for a currency (ISO 4217, e.g. USD): days the FX market for that currency does not trade. start defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| end | – | – | – |
| start | – | – | – |
No output schema declared.
No examples provided.
get_holidays Holidays for a calendar ~81
Holidays for one calendar by code (e.g. USD.FX). start defaults to today; pass an earlier start for historical holidays, end to bound forward dates. Rows carry original_date when a holiday is observed on a shifted date, plus half-day and early-close details.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | yes | – |
| end | – | – | – |
| start | – | – | – |
No output schema declared.
No examples provided.
get_weekends Weekend definitions ~54
Weekend definitions and working weekends for one calendar code (e.g. USD.FX). weekend_days is the definition in force today (ISO weekday numbers); weekend_definitions carries the full history.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | yes | – |
No output schema declared.
No examples provided.
is_business_day Is it a business day? ~147
Is a date a business day? Answers for one or several calendars at once and says why not (holiday name, weekend) or flags a half day / early close. calendars: one or more calendar codes from list_calendars, e.g. ["USD.FX", "EUR.FX"] for a EUR/USD FX trade, ["XNYS.SETTLE"] for NYSE settlement, ["TARGET2.PAY"] for euro payments, ["GBLON.BANK"] for London banks. A date counts as a business day only when it is open in every calendar given. date defaults to today (yyyy-mm-dd).
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | array | yes | – |
| date | – | – | – |
No output schema declared.
No examples provided.
list_calendars List calendars ~63
List published holiday calendars available to your plan. Optional calendar_type filters by family (CURRENCY_FX, CURRENCY_NON_CLEARING, FINANCIAL_CENTRE, PAYMENT_SYSTEM, EXCHANGE_TRADING, EXCHANGE_SETTLEMENT).
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_type | – | – | – |
No output schema declared.
No examples provided.
list_currencies List currencies ~24
List covered currencies (ISO 4217) with issuing country and issuer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_exchanges List exchanges ~27
List covered exchanges (ISO 10383 MIC) with country, city, and timezone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_financial_centres List financial centres ~26
List covered financial centres (UN/LOCODE) with country and timezone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_payment_systems List payment systems ~24
List covered payment systems with operator, type, currency, and country.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
market_status Market open/closed status ~85
Live open/half/closed status for exchanges, evaluated against real trading hours and today's trading holidays in each exchange's timezone. Includes next_open_at and next_close_at timestamps. Pass a MIC (e.g. XNYS) for one market or omit it for all. Requires a plan with exchange trading data (Free, Exchange, or All-in-one).
| Name | Type | Req | Description |
|---|---|---|---|
| market | – | – | – |
No output schema declared.
No examples provided.
payment_system_holidays Payment system holidays ~55
Payment system holidays (e.g. TARGET2, FEDWIRE): days the system does not process or settle. start defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| payment_system | string | yes | – |
| start | – | – | – |
No output schema declared.
No examples provided.
settlement_holidays Exchange settlement holidays ~59
Exchange settlement holidays for a market (ISO 10383 MIC, e.g. XNYS): days clearing and settlement cannot take place. start defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| market | string | yes | – |
| start | – | – | – |
No output schema declared.
No examples provided.
trading_holidays Exchange trading holidays ~71
Exchange trading holidays for a market (ISO 10383 MIC, e.g. XNYS): days the exchange is closed for trading, including shortened sessions (half_day and early_close_time fields). start defaults to today.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| market | string | yes | – |
| start | – | – | – |
No output schema declared.
No examples provided.
How do I install the TradingCalendars MCP server?
TradingCalendars is a hosted endpoint at https://api.tradingcalendars.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 · api.tradingcalendars.com
claude mcp add --transport http com-tradingcalendars-holidays 'https://api.tradingcalendars.com/mcp'
What is the TradingCalendars MCP server?
TradingCalendars is an MCP server listed in the public MCP registry as com.tradingcalendars/holidays. Business days, T+N settlement dates and holidays for FX, banks, payments and exchanges. This page covers its hosted endpoint (https://api.tradingcalendars.com/mcp).
Is the TradingCalendars MCP server safe to use?
TradingCalendars scores 68 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 TradingCalendars MCP server expose?
TradingCalendars exposes 17 tools: list_calendars, get_holidays, fx_market_holidays, currency_non_clearing_days, bank_holidays, and 12 more. Their descriptions and schemas cost roughly 1,230 tokens of context every time the server is loaded.
Does the TradingCalendars MCP server require authentication?
No. We connected to TradingCalendars without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TradingCalendars MCP server still maintained?
TradingCalendars 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.