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.

Trading Calendar & Public Holidays (x402)

REMOTE · HANDELSKALENDER-API.PAGES.DEV

Stock exchange trading days, hours, live market status (28 exchanges) and holidays (247 countries).

+4 this week 75 Trust /100

Last scanned (18 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 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 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. 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. 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
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1176 tokens (~235/item across 5 items; 5 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 69

    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 21 Nov 2026 · Probed https://handelskalender-api.pages.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=handelskalender-api.pages.dev CN=YE2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA384 5f309d68ef1766c13e3713a6eb1dcb9b91e
SANs: *.handelskalender-api.pages.dev, handelskalender-api.pages.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of handelskalender-api.pages.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
pages.dev. No DS 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://handelskalender-api.pages.dev/mcp Verified 200
http (plaintext) http://handelskalender-api.pages.dev/mcp HTTPS enforced 301 https://handelskalender-api.pages.dev/mcp
MCP tools · 5 exposed · ~1,124 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
business_day ~289

Use when an agent must know if a date is a business day in a country, or compute a due date: weekend or holiday (with name), previous/next business day, date plus N business days (add=), business days until a date (to=). 247 countries, 2026-2028, optional state/province (region=), local weekends (e.g. Fri-Sat). Bad input: HTTP 400, no charge. Price: 0.002 USDC per successful call (x402).

NameTypeReqDescription
addstring–Optional: number of business days to add (negative = go back), -260 to 260.
countrystringyes2-letter ISO country code, e.g. AT, DE, US, GB, FR, JP, IN, BR, AE. 247 countries; free list: GET /v1/holiday-countries.
datestring–Day as YYYY-MM-DD. Optional, default: today (UTC).
regionstring–Optional state/province for regional holidays, e.g. BY or DE-BY (Bavaria), CA (California), 9 (Vienna). Listed per country in GET /v1/holiday-countries.
tostring–Optional end date YYYY-MM-DD (>= date): count business days from date to it, both included.

No output schema declared.

No examples provided.

market_status ~154

Use when an agent needs to know right now which stock exchanges are open: open, lunch break, pre-market, after-hours or closed (with holiday name), local time, exact next open and close in UTC. One call checks up to 28 exchanges (default all) incl. NYSE, Nasdaq, LSE, Xetra, Euronext, Tokyo, HKEX, Shanghai, ASX. Official exchange calendars only; unknown exchange: HTTP 400, no charge. Price: 0.002 USDC per successful call (x402).

NameTypeReqDescription
exchangesstring–Comma-separated MIC codes or names, e.g. XNYS,XETR,XTKS. Optional, default: all exchanges.

No output schema declared.

No examples provided.

public_holidays ~232

Use when an agent needs all public holidays of a country for a year (planning deliveries, payments, deadlines, staffing). 247 countries, 2026-2028, optional state/province (region=) for regional holidays. English and local names, weekend days of the country, moon-dependent dates flagged as estimated. Bad input: HTTP 400 before payment, no charge. Price: 0.002 USDC per successful call (x402).

NameTypeReqDescription
countrystringyes2-letter ISO country code, e.g. AT, DE, US, GB, FR, JP, IN, BR, AE. 247 countries; free list: GET /v1/holiday-countries.
regionstring–Optional state/province for regional holidays, e.g. BY or DE-BY (Bavaria), CA (California), 9 (Vienna). Listed per country in GET /v1/holiday-countries.
yearstring–Year, e.g. 2027. Optional, default: current year. Covered: 2026-2028.

No output schema declared.

No examples provided.

trading_calendar ~208

Use when an agent plans ahead and needs every closure of a stock exchange for a whole year: holiday names, half days, late openings, regular hours, count of trading days. 28 exchanges incl. NYSE, Nasdaq, LSE, Xetra, Euronext, SIX, Tokyo, HKEX, Shanghai, ASX. Official exchange calendars only; bad input or uncovered year: HTTP 400, no charge. Price: 0.002 USDC per successful call (x402).

NameTypeReqDescription
exchangestringyesExchange MIC code, e.g. XNYS (NYSE), XNAS (Nasdaq), XLON (London), XETR (Xetra), XPAR (Paris), XTKS (Tokyo), XHKG (Hong Kong). Common names also work (NYSE, Xetra, LSE). Free list: GET /v1/exchanges.
yearstring–Year, e.g. 2026. Optional, default: current year.

No output schema declared.

No examples provided.

trading_day ~241

Use when an agent needs to know if a stock exchange trades on a given day (default today) before scheduling orders, reports or alerts. 28 exchanges incl. NYSE, Nasdaq, LSE, Xetra, Euronext, SIX, Tokyo, HKEX, Shanghai, ASX. Returns holiday name, hours in local time + UTC, half days, lunch breaks, pre/after-market (Nasdaq, Xetra), live status, next open/close, previous/next trading day. Official exchange calendars only; bad input: HTTP 400, no charge. Price: 0.002 USDC per successful call (x402).

NameTypeReqDescription
datestring–Day as YYYY-MM-DD. Optional, default: today in the exchange's time zone.
exchangestringyesExchange MIC code, e.g. XNYS (NYSE), XNAS (Nasdaq), XLON (London), XETR (Xetra), XPAR (Paris), XTKS (Tokyo), XHKG (Hong Kong). Common names also work (NYSE, Xetra, LSE). Free list: GET /v1/exchanges.

No output schema declared.

No examples provided.

Install

How do I install the Trading Calendar & Public Holidays (x402) MCP server?

Trading Calendar & Public Holidays (x402) is a hosted endpoint at https://handelskalender-api.pages.dev/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 · handelskalender-api.pages.dev

# add to Claude Code
claude mcp add --transport http vstockma-handelskalender-api 'https://handelskalender-api.pages.dev/mcp'
Common questions

What is the Trading Calendar & Public Holidays (x402) MCP server?

Trading Calendar & Public Holidays (x402) is an MCP server listed in the public MCP registry as io.github.vstockma/handelskalender-api. Stock exchange trading days, hours, live market status (28 exchanges) and holidays (247 countries). This page covers its hosted endpoint (https://handelskalender-api.pages.dev/mcp).

Is the Trading Calendar & Public Holidays (x402) MCP server safe to use?

Trading Calendar & Public Holidays (x402) scores 75 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 Trading Calendar & Public Holidays (x402) MCP server expose?

Trading Calendar & Public Holidays (x402) exposes 5 tools: trading_day, trading_calendar, market_status, public_holidays, business_day. Their descriptions and schemas cost roughly 1,124 tokens of context every time the server is loaded.

Does the Trading Calendar & Public Holidays (x402) MCP server require authentication?

No. We connected to Trading Calendar & Public Holidays (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Trading Calendar & Public Holidays (x402) MCP server still maintained?

Trading Calendar & Public Holidays (x402) is still listed as active in the MCP registry. We last reached this channel on 21 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 Trading Calendar & Public Holidays (x402) MCP server?

VerifyMCP ran 13 checks on Trading Calendar & Public Holidays (x402), 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.