
Tradingcalendars MCP server
Which MCP servers are Tradingcalendars's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-03
- Registry namecom.tradingcalendars/holidaysverified in the MCP registry
The registry name sits under tradingcalendars.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-03
- Tools17
- Server calls itselfTradingCalendars
- Protocol version2025-06-18
On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 115 ms.
- Its tools do every use case we checked: Validate fx value dates against currency non-clearing days; Flag observed dates and early closes in settlement logic.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- For "Validate fx value dates against currency non-clearing days", the likely first call is currency_non_clearing_days.
- add_business_days change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 13 of 17 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer144 ms
- Space in an agent's context≈ 2,233 tokensthe definitions of all its tools (17), which an agent carries on every turn
- Tool definitionsC · 71 of 100
- Typed results0 of 17 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 13 of 17
- Not saying whether it only reads or can destroy: 17 of 17
What an agent can do with it
- can do · Validate fx value dates against currency non-clearing days
- not sure · Schedule jobs around exchange open, half-day and closed status
- can do · Flag observed dates and early closes in settlement logic
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: add_business_days
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_calendarsList 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).
get_holidaysHolidays 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…
fx_market_holidaysFX market holidays for a currency (ISO 4217, e.g. USD): days the FX market for that currency does not trade. start defaults to today.
currency_non_clearing_daysCurrency 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.
bank_holidaysBank holidays for a financial centre (UN/LOCODE, e.g. USNYC): days retail and commercial banks are closed. start defaults to today.
payment_system_holidaysPayment system holidays (e.g. TARGET2, FEDWIRE): days the system does not process or settle. start defaults to today.
trading_holidaysExchange 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.
settlement_holidaysExchange settlement holidays for a market (ISO 10383 MIC, e.g. XNYS): days clearing and settlement cannot take place. start defaults to today.
list_currenciesList covered currencies (ISO 4217) with issuing country and issuer.
list_exchangesList covered exchanges (ISO 10383 MIC) with country, city, and timezone.
list_financial_centresList covered financial centres (UN/LOCODE) with country and timezone.
list_payment_systemsList covered payment systems with operator, type, currency, and country.
get_weekendsWeekend 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.
market_statusLive 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…
is_business_dayIs 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…
add_business_daysDate 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…
business_days_betweenNumber 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"holidays": {
"type": "http",
"url": "https://api.tradingcalendars.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http tradingcalendars https://api.tradingcalendars.com/mcpclaude.ai, ChatGPT and other clients: add https://api.tradingcalendars.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.