Business-Day Oracle
REMOTE · BIZDAY.NOAHSARCH.TECH
Working days, ISDA conventions and deadlines for 250 countries and 30 financial markets.
Available components
Last scanned (4 hours ago)
Scores higher than 54% 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, 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 Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4056 tokens (~405/item across 10 items; 8 tools + 2 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 Management17
- Stability observed for 5 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 +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.
- 3 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.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 66
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://bizday.noahsarch.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noahsarch.tech | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 470026e1ea46ecc0e06d5a5a9df0965 |
| SANs: noahsarch.tech, *.noahsarch.tech | ||||||
| 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 bizday.noahsarch.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| noahsarch.tech. | 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://bizday.noahsarch.tech/mcp | Verified | 200 | |
| http (plaintext) | http://bizday.noahsarch.tech/mcp | Inconclusive | 406 |
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_working_days Add or subtract working days ~530
Move N working days from a date, skipping weekends and holidays; returns the end date and every skipped day with its reason. Delivery promises, SLA clocks, payment terms in business days. Example: start_date '2026-12-23', days 5, country 'DE', subdivision 'BY'. Calendar selection: country (ISO 3166-1 alpha-2, e.g. 'SA', 'DE', 'US') or market (MIC, e.g. 'XNYS', 'XLON'); optional subdivision (state/province/emirate code from list_calendars), categories (e.g. ['public','bank']), weekend override (['FRI','SAT']), extra_holidays (company/contract dates). Weekend defaults to the country's legal weekend. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Holiday categories to count as non-working; default ['public']. Others per country: bank, government, school, optional, half_day, catholic… |
| count_start_day | boolean | – | If true and start_date is a working day it counts as day 1. Default false (start the day after). |
| country | – | – | ISO 3166-1 alpha-2 country code. Required unless market is given. |
| days | integer | yes | Working days to add; negative counts backwards. |
| extra_holidays | – | – | Additional non-working ISO dates (company closures, contract-specific days). |
| include_estimated_holidays | boolean | – | Count projected lunar/moon-sighted holidays as non-working (true) or ignore them until announced (false). |
| language | – | – | Language for holiday names where available (e.g. 'ar', 'de', 'en_US'). Default: the country's own. |
| market | – | – | Financial market MIC (XNYS, XLON, XETR, XHKG, XJPX, XSAU…) — trading/settlement calendar instead of a country. |
| start_date | string | yes | ISO date to count from. |
| subdivision | – | – | Sub-national code (US 'CA', DE 'BY', AE 'DU', CA 'ON', AU 'NSW', IN 'KA'…). See list_calendars. |
| weekend | – | – | Override the weekend, e.g. ['FRI','SAT'] or ['SUN']. Default: the country's legal weekend. |
Structured output declared, but exposes no named fields.
No examples provided.
compute_deadline Compute a deadline with an explanation trail ~667
Compute the end of a period ('within 30 calendar days', '10 working days', '3 months') from a start date under explicit counting rules, roll it by the chosen convention when it lands on a non-working day, and return raw vs final deadline, skipped days and a step-by-step explanation plus a disclaimer. Pass the rules the contract/law states; defaults are the common ones. Example: start_date '2026-11-26', period 7, unit 'calendar_days', country 'GB'. Calendar selection: country (ISO 3166-1 alpha-2, e.g. 'SA', 'DE', 'US') or market (MIC, e.g. 'XNYS', 'XLON'); optional subdivision (state/province/emirate code from list_calendars), categories (e.g. ['public','bank']), weekend override (['FRI','SAT']), extra_holidays (company/contract dates). Weekend defaults to the country's legal weekend. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Holiday categories to count as non-working; default ['public']. Others per country: bank, government, school, optional, half_day, catholic… |
| convention | string | – | What to do when the raw deadline lands on a non-working day. Default following (roll to the next working day); 'none' leaves it. |
| country | – | – | ISO 3166-1 alpha-2 country code. Required unless market is given. |
| exclude_start_day | boolean | – | Day 1 is the day after start_date (true, the common convention) or start_date itself (false). |
| extra_holidays | – | – | Additional non-working ISO dates (company closures, contract-specific days). |
| include_estimated_holidays | boolean | – | Count projected lunar/moon-sighted holidays as non-working (true) or ignore them until announced (false). |
| language | – | – | Language for holiday names where available (e.g. 'ar', 'de', 'en_US'). Default: the country's own. |
| market | – | – | Financial market MIC (XNYS, XLON, XETR, XHKG, XJPX, XSAU…) — trading/settlement calendar instead of a country. |
| month_end_clamp | boolean | – | For months: clamp 31 Jan + 1 month to 28/29 Feb (true) or overflow into March (false). |
| period | integer | yes | Length of the period; negative counts backwards. |
| start_date | string | yes | ISO date the period runs from (service, invoice, filing date…). |
| subdivision | – | – | Sub-national code (US 'CA', DE 'BY', AE 'DU', CA 'ON', AU 'NSW', IN 'KA'…). See list_calendars. |
| unit | string | yes | calendar_days | working_days | months. |
| weekend | – | – | Override the weekend, e.g. ['FRI','SAT'] or ['SUN']. Default: the country's legal weekend. |
Structured output declared, but exposes no named fields.
No examples provided.
is_working_day Is this date a working day? ~469
Say whether a date is a working day in a country/subdivision or market, and why not (weekend, holiday name, holiday observed, projected lunar holiday). Example: date '2027-03-10', country 'SA'. Calendar selection: country (ISO 3166-1 alpha-2, e.g. 'SA', 'DE', 'US') or market (MIC, e.g. 'XNYS', 'XLON'); optional subdivision (state/province/emirate code from list_calendars), categories (e.g. ['public','bank']), weekend override (['FRI','SAT']), extra_holidays (company/contract dates). Weekend defaults to the country's legal weekend. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Holiday categories to count as non-working; default ['public']. Others per country: bank, government, school, optional, half_day, catholic… |
| country | – | – | ISO 3166-1 alpha-2 country code. Required unless market is given. |
| date | string | yes | ISO date YYYY-MM-DD. |
| extra_holidays | – | – | Additional non-working ISO dates (company closures, contract-specific days). |
| include_estimated_holidays | boolean | – | Count projected lunar/moon-sighted holidays as non-working (true) or ignore them until announced (false). |
| language | – | – | Language for holiday names where available (e.g. 'ar', 'de', 'en_US'). Default: the country's own. |
| market | – | – | Financial market MIC (XNYS, XLON, XETR, XHKG, XJPX, XSAU…) — trading/settlement calendar instead of a country. |
| subdivision | – | – | Sub-national code (US 'CA', DE 'BY', AE 'DU', CA 'ON', AU 'NSW', IN 'KA'…). See list_calendars. |
| weekend | – | – | Override the weekend, e.g. ['FRI','SAT'] or ['SUN']. Default: the country's legal weekend. |
Structured output declared, but exposes no named fields.
No examples provided.
list_calendars Supported countries, markets, subdivisions, weekends ~151
Discover calendars: without arguments, all 250 countries and 30 markets; with a country code, its legal weekend, subdivision codes, holiday categories, languages, year range and public sources. Free. Example: country 'US'. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | Country code or market MIC for details (weekend, subdivisions, categories, languages, sources). Omit to list all 250 countries and 30 markets. |
Structured output declared, but exposes no named fields.
No examples provided.
list_holidays List holidays for a year ~479
All holidays of a year for a country/subdivision/categories or a market, each with local and English names, whether it is observed/shifted, projected (lunar), on a weekend, and whether it counts as non-working. Example: year 2027, country 'IN', subdivision 'KA'. Calendar selection: country (ISO 3166-1 alpha-2, e.g. 'SA', 'DE', 'US') or market (MIC, e.g. 'XNYS', 'XLON'); optional subdivision (state/province/emirate code from list_calendars), categories (e.g. ['public','bank']), weekend override (['FRI','SAT']), extra_holidays (company/contract dates). Weekend defaults to the country's legal weekend. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Holiday categories to count as non-working; default ['public']. Others per country: bank, government, school, optional, half_day, catholic… |
| country | – | – | ISO 3166-1 alpha-2 country code. Required unless market is given. |
| extra_holidays | – | – | Additional non-working ISO dates (company closures, contract-specific days). |
| include_estimated_holidays | boolean | – | Count projected lunar/moon-sighted holidays as non-working (true) or ignore them until announced (false). |
| language | – | – | Language for holiday names where available (e.g. 'ar', 'de', 'en_US'). Default: the country's own. |
| market | – | – | Financial market MIC (XNYS, XLON, XETR, XHKG, XJPX, XSAU…) — trading/settlement calendar instead of a country. |
| subdivision | – | – | Sub-national code (US 'CA', DE 'BY', AE 'DU', CA 'ON', AU 'NSW', IN 'KA'…). See list_calendars. |
| weekend | – | – | Override the weekend, e.g. ['FRI','SAT'] or ['SUN']. Default: the country's legal weekend. |
| year | integer | yes | Calendar year. |
Structured output declared, but exposes no named fields.
No examples provided.
next_holiday Next holiday(s) from a date ~472
The next N holidays on or after a date with days_until and projection flags. Example: from_date '2026-11-01', country 'JP', count 3. Calendar selection: country (ISO 3166-1 alpha-2, e.g. 'SA', 'DE', 'US') or market (MIC, e.g. 'XNYS', 'XLON'); optional subdivision (state/province/emirate code from list_calendars), categories (e.g. ['public','bank']), weekend override (['FRI','SAT']), extra_holidays (company/contract dates). Weekend defaults to the country's legal weekend. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Holiday categories to count as non-working; default ['public']. Others per country: bank, government, school, optional, half_day, catholic… |
| count | integer | – | How many upcoming holidays to return. |
| country | – | – | ISO 3166-1 alpha-2 country code. Required unless market is given. |
| extra_holidays | – | – | Additional non-working ISO dates (company closures, contract-specific days). |
| from_date | string | yes | ISO date to search from (inclusive). |
| include_estimated_holidays | boolean | – | Count projected lunar/moon-sighted holidays as non-working (true) or ignore them until announced (false). |
| language | – | – | Language for holiday names where available (e.g. 'ar', 'de', 'en_US'). Default: the country's own. |
| market | – | – | Financial market MIC (XNYS, XLON, XETR, XHKG, XJPX, XSAU…) — trading/settlement calendar instead of a country. |
| subdivision | – | – | Sub-national code (US 'CA', DE 'BY', AE 'DU', CA 'ON', AU 'NSW', IN 'KA'…). See list_calendars. |
| weekend | – | – | Override the weekend, e.g. ['FRI','SAT'] or ['SUN']. Default: the country's legal weekend. |
Structured output declared, but exposes no named fields.
No examples provided.
roll_date Adjust a date by business-day convention ~515
Apply a business-day convention (following, modified following, preceding, modified preceding) to a date on a country or market calendar — payment dates, coupon dates, settlement, SLA due dates. Example: date '2026-05-31', convention 'modified_following', market 'XLON'. Calendar selection: country (ISO 3166-1 alpha-2, e.g. 'SA', 'DE', 'US') or market (MIC, e.g. 'XNYS', 'XLON'); optional subdivision (state/province/emirate code from list_calendars), categories (e.g. ['public','bank']), weekend override (['FRI','SAT']), extra_holidays (company/contract dates). Weekend defaults to the country's legal weekend. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Holiday categories to count as non-working; default ['public']. Others per country: bank, government, school, optional, half_day, catholic… |
| convention | string | – | Business-day convention: following | modified_following (ISDA: forward unless it crosses month end, then back) | preceding | modified_preceding. |
| country | – | – | ISO 3166-1 alpha-2 country code. Required unless market is given. |
| date | string | yes | ISO date to adjust. |
| extra_holidays | – | – | Additional non-working ISO dates (company closures, contract-specific days). |
| include_estimated_holidays | boolean | – | Count projected lunar/moon-sighted holidays as non-working (true) or ignore them until announced (false). |
| language | – | – | Language for holiday names where available (e.g. 'ar', 'de', 'en_US'). Default: the country's own. |
| market | – | – | Financial market MIC (XNYS, XLON, XETR, XHKG, XJPX, XSAU…) — trading/settlement calendar instead of a country. |
| subdivision | – | – | Sub-national code (US 'CA', DE 'BY', AE 'DU', CA 'ON', AU 'NSW', IN 'KA'…). See list_calendars. |
| weekend | – | – | Override the weekend, e.g. ['FRI','SAT'] or ['SUN']. Default: the country's legal weekend. |
Structured output declared, but exposes no named fields.
No examples provided.
working_days_between Count working days between two dates ~511
Count working days between two dates with endpoint control; lists the non-working days. Leave cost, lateness, elapsed business days. Example: '2026-05-18' → '2026-06-05', country 'AE', inclusive 'both'. Calendar selection: country (ISO 3166-1 alpha-2, e.g. 'SA', 'DE', 'US') or market (MIC, e.g. 'XNYS', 'XLON'); optional subdivision (state/province/emirate code from list_calendars), categories (e.g. ['public','bank']), weekend override (['FRI','SAT']), extra_holidays (company/contract dates). Weekend defaults to the country's legal weekend. Response: result plus data_confidence (high = fixed-date calendar; medium = a lunar/moon-sighted or projected holiday is involved, or the caller overrode the weekend), estimated_items[] naming each projected date, sources[] (public references behind the calendar), data_version and warnings[].
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Holiday categories to count as non-working; default ['public']. Others per country: bank, government, school, optional, half_day, catholic… |
| country | – | – | ISO 3166-1 alpha-2 country code. Required unless market is given. |
| end_date | string | yes | ISO date; may be before start_date (negative result). |
| extra_holidays | – | – | Additional non-working ISO dates (company closures, contract-specific days). |
| include_estimated_holidays | boolean | – | Count projected lunar/moon-sighted holidays as non-working (true) or ignore them until announced (false). |
| inclusive | string | – | Which endpoints count: both (default) | start | end | none. |
| language | – | – | Language for holiday names where available (e.g. 'ar', 'de', 'en_US'). Default: the country's own. |
| market | – | – | Financial market MIC (XNYS, XLON, XETR, XHKG, XJPX, XSAU…) — trading/settlement calendar instead of a country. |
| start_date | string | yes | ISO date. |
| subdivision | – | – | Sub-national code (US 'CA', DE 'BY', AE 'DU', CA 'ON', AU 'NSW', IN 'KA'…). See list_calendars. |
| weekend | – | – | Override the weekend, e.g. ['FRI','SAT'] or ['SUN']. Default: the country's legal weekend. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Business-Day Oracle MCP server?
Business-Day Oracle is a hosted endpoint at https://bizday.noahsarch.tech/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 · bizday.noahsarch.tech
claude mcp add --transport http tech-noahsarch-business-day-oracle 'https://bizday.noahsarch.tech/mcp'
What is the Business-Day Oracle MCP server?
Business-Day Oracle is an MCP server listed in the public MCP registry as tech.noahsarch/business-day-oracle. Working days, ISDA conventions and deadlines for 250 countries and 30 financial markets. This page covers its hosted endpoint (https://bizday.noahsarch.tech/mcp).
Is the Business-Day Oracle MCP server safe to use?
Business-Day Oracle scores 69 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 Oracle MCP server expose?
Business-Day Oracle exposes 8 tools: is_working_day, add_working_days, working_days_between, roll_date, compute_deadline, and 3 more. Their descriptions and schemas cost roughly 3,794 tokens of context every time the server is loaded.
Does the Business-Day Oracle MCP server require authentication?
No. We connected to Business-Day Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Business-Day Oracle MCP server still maintained?
Business-Day Oracle 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.