# Business Day Calendars (remote · business-days.quietworklabs.workers.dev)

NYSE, Federal Reserve, TARGET2 and UK business days, holidays and T+N settlement dates.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `business-days.quietworklabs.workers.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-quietworklabs-business-days-business-days/business-days.md), [page](https://verifymcp.io/servers/dev-workers-quietworklabs-business-days-business-days/business-days)

## Channel facts

- Endpoint: `https://business-days.quietworklabs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-workers-quietworklabs-business-days-business 'https://business-days.quietworklabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-quietworklabs-business-days-business": {
      "url": "https://business-days.quietworklabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-quietworklabs-business-days-business": {
      "type": "http",
      "url": "https://business-days.quietworklabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-quietworklabs-business-days-business]
url = "https://business-days.quietworklabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-quietworklabs-business-days-business": {
      "type": "remote",
      "url": "https://business-days.quietworklabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-quietworklabs-business-days-business --url 'https://business-days.quietworklabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-quietworklabs-business-days-business:
    url: "https://business-days.quietworklabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-quietworklabs-business-days-business": {
      "Transport": "http",
      "Url": "https://business-days.quietworklabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-quietworklabs-business-days-business -t streamable-http -u 'https://business-days.quietworklabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-quietworklabs-business-days-business": {
      "type": "http",
      "url": "https://business-days.quietworklabs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 73, +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.

### 2026-11-01 (score 72, +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.

### 2026-10-30 (score 71, +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.

### 2026-10-28 (score 70, +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.

### 2026-10-26 (score 69, +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.

### 2026-10-24 (score 68, +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.

### 2026-10-22 (score 67, +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.

### 2026-10-19 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `is_business_day` (~164 tokens)

Is a date a business day on the given calendars

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.

Input parameters:

- `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, required): Date YYYY-MM-DD

### `add_business_days` (~177 tokens)

Add or subtract N business days

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.

Input parameters:

- `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, required): Start date YYYY-MM-DD
- `days` (string, required): Business days to add, -2000..2000

### `settlement_date` (~145 tokens)

T+N settlement date for a trade date

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.

Input parameters:

- `calendars` (string): Calendars; default XNYS,FED
- `t` (string): Settlement lag in business days (0-10). Default 1
- `trade_date` (string, required): Trade date YYYY-MM-DD

### `business_days_between` (~190 tokens)

Count business days between two dates

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.

Input parameters:

- `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, required): End date YYYY-MM-DD
- `inclusive` (string): true to count the start date too
- `start` (string, required): Start date YYYY-MM-DD

### `adjust_date` (~181 tokens)

Roll a date to a business day (modified following etc.)

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.

Input parameters:

- `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, required): Date YYYY-MM-DD

### `list_holidays` (~146 tokens)

Holidays (and NYSE early closes) for a calendar and year

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.

Input parameters:

- `calendar` (string, required): XNYS, FED, TARGET2 or UK-ENG
- `year` (string, required): Year 2000-2099

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-quietworklabs-business-days-business-days/business-days#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 67
- 2026-10-22: 67
- 2026-10-21: 66
- 2026-10-20: 66
- 2026-10-19: 66
- 2026-10-18: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://business-days.quietworklabs.workers.dev/mcp
- Website: https://business-days.quietworklabs.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-quietworklabs-business-days-business-days/business-days.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-quietworklabs-business-days-business-days/business-days/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-workers-quietworklabs-business-days-business-days/business-days.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-quietworklabs-business-days-business-days/business-days