Business Day Calendars
REMOTE · BUSINESS-DAYS.QUIETWORKLABS.WORKERS.DEV
NYSE, Federal Reserve, TARGET2 and UK business days, holidays and T+N settlement dates.
Available components
Last scanned (11 hours ago)
Scores higher than 60% 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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1248 tokens (~208/item across 6 items; 6 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 Management60
- Stability observed for 18 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 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.
- 19 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
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://business-days.quietworklabs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quietworklabs.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6203662d048034ad6156b34972b93b5ae9a |
| SANs: *.quietworklabs.workers.dev, quietworklabs.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 business-days.quietworklabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.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://business-days.quietworklabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://business-days.quietworklabs.workers.dev/mcp | Inconclusive | 405 |
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 or subtract N business days ~177
Adds (or with negative days subtracts) N business days to a date on a joint calendar (NYSE, Fedwire/FedACH, TARGET2, UK) and lists the holidays skipped. Deterministic, no AI. Price: $0.001 USDC per call via x402 (Base); the first 5 calls per day per client are free.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | string | – | Comma list of calendars; a day is a business day only if open in all. XNYS (NYSE), FED (Fedwire/FedACH), TARGET2 (EUR), UK-ENG. Aliases: NYSE, US, ACH, EUR, UK. Default FED. |
| date | string | yes | Start date YYYY-MM-DD |
| days | string | yes | Business days to add, -2000..2000 |
No output schema declared.
No examples provided.
adjust_date Roll a date to a business day (modified following etc.) ~181
Rolls a date that falls on a weekend or holiday using a business-day convention: following, modified_following, preceding, modified_preceding. Typical for payment, coupon and invoice due dates. Deterministic, no AI. Price: $0.001 USDC per call via x402 (Base); the first 5 calls per day per client are free.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | string | – | Comma list of calendars; a day is a business day only if open in all. XNYS (NYSE), FED (Fedwire/FedACH), TARGET2 (EUR), UK-ENG. Aliases: NYSE, US, ACH, EUR, UK. Default FED. |
| convention | string | – | following | modified_following | preceding | modified_preceding. Default modified_following |
| date | string | yes | Date YYYY-MM-DD |
No output schema declared.
No examples provided.
business_days_between Count business days between two dates ~190
Counts business days between two dates on a joint calendar: days after start up to and including end (inclusive=true also counts start). Negative if end is before start. Lists weekday holidays in range. Max 10 years. Deterministic, no AI. Price: $0.001 USDC per call via x402 (Base); the first 5 calls per day per client are free.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | string | – | Comma list of calendars; a day is a business day only if open in all. XNYS (NYSE), FED (Fedwire/FedACH), TARGET2 (EUR), UK-ENG. Aliases: NYSE, US, ACH, EUR, UK. Default FED. |
| end | string | yes | End date YYYY-MM-DD |
| inclusive | string | – | true to count the start date too |
| start | string | yes | Start date YYYY-MM-DD |
No output schema declared.
No examples provided.
is_business_day Is a date a business day on the given calendars ~164
Whether a date is a business day on one or more settlement calendars (NYSE, Fedwire/FedACH, TARGET2, UK), which holiday closes it, NYSE early closes, and the previous/next business day. Deterministic, no AI. Price: $0.001 USDC per call via x402 (Base); the first 5 calls per day per client are free.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | string | – | Comma list of calendars; a day is a business day only if open in all. XNYS (NYSE), FED (Fedwire/FedACH), TARGET2 (EUR), UK-ENG. Aliases: NYSE, US, ACH, EUR, UK. Default FED. |
| date | string | yes | Date YYYY-MM-DD |
No output schema declared.
No examples provided.
list_holidays Holidays (and NYSE early closes) for a calendar and year ~146
Lists closing days for one calendar and year (2000-2099): NYSE full closures and 1 pm early closes, Federal Reserve (Fedwire/FedACH) holidays with Saturday/Sunday observance rules, TARGET2 closing days, UK England & Wales bank holidays with substitute days. Weekend-only holidays with no weekday closure are omitted. Deterministic, no AI. Price: $0.001 USDC per call via x402 (Base); the first 5 calls per day per client are free.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | yes | XNYS, FED, TARGET2 or UK-ENG |
| year | string | yes | Year 2000-2099 |
No output schema declared.
No examples provided.
settlement_date T+N settlement date for a trade date ~145
Settlement date T+N for a trade date on a joint calendar. Default XNYS,FED with t=1 (US equities since 28 May 2024). If the trade date is not a business day it is first rolled to the next one. Deterministic, no AI. Price: $0.001 USDC per call via x402 (Base); the first 5 calls per day per client are free.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | string | – | Calendars; default XNYS,FED |
| t | string | – | Settlement lag in business days (0-10). Default 1 |
| trade_date | string | yes | Trade date YYYY-MM-DD |
No output schema declared.
No examples provided.
How do I install the Business Day Calendars MCP server?
Business Day Calendars is a hosted endpoint at https://business-days.quietworklabs.workers.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 · business-days.quietworklabs.workers.dev
claude mcp add --transport http dev-workers-quietworklabs-business-days-business 'https://business-days.quietworklabs.workers.dev/mcp'
What is the Business Day Calendars MCP server?
Business Day Calendars is an MCP server listed in the public MCP registry as dev.workers.quietworklabs.business-days/business-days. NYSE, Federal Reserve, TARGET2 and UK business days, holidays and T+N settlement dates. This page covers its hosted endpoint (https://business-days.quietworklabs.workers.dev/mcp).
Is the Business Day Calendars MCP server safe to use?
Business Day Calendars scores 73 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 Business Day Calendars MCP server expose?
Business Day Calendars exposes 6 tools: is_business_day, add_business_days, settlement_date, business_days_between, adjust_date, list_holidays. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.
Does the Business Day Calendars MCP server require authentication?
No. We connected to Business Day Calendars without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Business Day Calendars MCP server still maintained?
Business Day Calendars 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 Business Day Calendars MCP server?
VerifyMCP ran 12 checks on Business Day Calendars, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Business Day Calendars: HTTPS. 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.