NZ Data API
REMOTE · NZDATA.ZAKWINS.WORKERS.DEV
New Zealand public holidays, working-day deadlines, IRD/NZBN/bank checks, GST. Pay per call via x402
Available components
Last scanned (9 hours ago)
Scores higher than 62% 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 Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 983 tokens (~122/item across 8 items; 8 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 Management57
- Stability observed for 17 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 4 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.
- 2 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 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.
- 28 Oct 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.
- 26 Oct 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.
- 24 Oct 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.
- 22 Oct 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.
- 20 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://nzdata.zakwins.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=zakwins.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53a079499bd87a61d7e458a5b7702c02b93 |
| SANs: *.zakwins.workers.dev, zakwins.workers.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 nzdata.zakwins.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://nzdata.zakwins.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://nzdata.zakwins.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 →
nz_gst NZ GST 15% calculator ~88
NZ GST 15% calculator (exclusive or inclusive). Paid tool: $0.001 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"amount":"115","mode":"inclusive"}
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | e.g. 115 |
| mode | string | – | e.g. inclusive |
No output schema declared.
No examples provided.
nz_holidays NZ public holidays 2022-2030 incl. Matariki, Mondayisation and optional regional anniversary day ~106
NZ public holidays 2022-2030 incl. Matariki, Mondayisation and optional regional anniversary day. Paid tool: $0.002 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"year":"2026","region":"auckland"}
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | e.g. auckland |
| year | string | – | e.g. 2026 |
No output schema declared.
No examples provided.
nz_validate_bank Validate an NZ bank account number check digit ~112
Validate an NZ bank account number check digit (IRD algorithms A-G/X), normalise BB-bbbb-AAAAAAA-SSS and identify the bank code. Paid tool: $0.001 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"number":"01-0902-0068389-00"}
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | – | e.g. 01-0902-0068389-00 |
No output schema declared.
No examples provided.
nz_validate_ird Validate NZ IRD/GST number check digit ~77
Validate NZ IRD/GST number check digit. Paid tool: $0.001 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"number":"49091850"}
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | – | e.g. 49091850 |
No output schema declared.
No examples provided.
nz_validate_nzbn Validate NZBN ~84
Validate NZBN (GTIN-13) check digit. Paid tool: $0.001 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"number":"9429041535134"}
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | – | e.g. 9429041535134 |
No output schema declared.
No examples provided.
nz_validate_phone Validate and normalise an NZ phone number to E.164 with type ~87
Validate and normalise an NZ phone number to E.164 with type. Paid tool: $0.001 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"number":"021 123 4567"}
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | – | e.g. 021 123 4567 |
No output schema declared.
No examples provided.
nz_working_days Count NZ working days between two dates inclusive ~161
Count NZ working days between two dates inclusive (weekends, public holidays, optional statutory Christmas shutdown presets oia|lgoima|building_act|rta). Paid tool: $0.002 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"start":"2026-10-01","end":"2026-10-31","region":"","preset":"none"}
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | e.g. 2026-10-31 |
| preset | string | – | e.g. none |
| region | string | – | e.g. (empty) |
| start | string | – | e.g. 2026-10-01 |
No output schema declared.
No examples provided.
nz_working_days_add Add N NZ working days to a date ~127
Add N NZ working days to a date (e.g. OIA 20 working-day deadline). Paid tool: $0.002 USDC on Base per call via x402 (an unpaid call returns PaymentRequired; retry with _meta["x402/payment"]). Example args: {"start":"2026-12-15","days":"20","preset":"oia"}
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | e.g. 20 |
| preset | string | – | e.g. oia |
| start | string | – | e.g. 2026-12-15 |
No output schema declared.
No examples provided.
How do I install the NZ Data API MCP server?
NZ Data API is a hosted endpoint at https://nzdata.zakwins.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 · nzdata.zakwins.workers.dev
claude mcp add --transport http dev-workers-zakwins-nzdata-nz-data-api 'https://nzdata.zakwins.workers.dev/mcp'
What is the NZ Data API MCP server?
NZ Data API is an MCP server listed in the public MCP registry as dev.workers.zakwins.nzdata/nz-data-api. New Zealand public holidays, working-day deadlines, IRD/NZBN/bank checks, GST. Pay per call via x402. This page covers its hosted endpoint (https://nzdata.zakwins.workers.dev/mcp).
Is the NZ Data API MCP server safe to use?
NZ Data API scores 74 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 NZ Data API MCP server expose?
NZ Data API exposes 8 tools: nz_holidays, nz_working_days, nz_working_days_add, nz_validate_ird, nz_validate_nzbn, and 3 more. Their descriptions and schemas cost roughly 842 tokens of context every time the server is loaded.
Does the NZ Data API MCP server require authentication?
No. We connected to NZ Data API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NZ Data API MCP server still maintained?
NZ Data API 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 NZ Data API MCP server?
VerifyMCP ran 12 checks on NZ Data API, 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 NZ Data API: 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.