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.

SA Business Calendar

REMOTE · CALENDAR.NAMKA.CLOUD · 2 COMPONENTS

South African business days, public holidays and SARS EMP201/VAT201 deadlines.

+4 this week 65 Trust /100

Last scanned (14 hours ago)

Scores higher than 46% 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 Security46
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 377 tokens (~62/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 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 6 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
What we tested

Checks we ran (11)

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

Checks we could not complete (2)

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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • 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 →

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

  • 19 Nov 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.

  • 17 Nov 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.

  • 15 Nov 26 +1

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

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 61

    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://calendar.namka.cloud/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=namka.cloud CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA256 2a1362a4fa3a8cdb132d370e4f139220
SANs: namka.cloud, calendar.namka.cloud, *.calendar.namka.cloud
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 calendar.namka.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cloud. DS published 7041 13 Verified
namka.cloud. 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://calendar.namka.cloud/mcp Verified 200
http (plaintext) http://calendar.namka.cloud/mcp Inconclusive 405
MCP tools · 6 exposed · ~377 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
add_business_days ~79

Add (or subtract, with a negative number) South African business days to a date, skipping weekends and SA public holidays. Use for payment terms, notice periods and delivery dates. (paid via Apify)

NameTypeReqDescription
datestringyesDate as YYYY-MM-DD
daysintegeryesBusiness days to add; negative to go back

No output schema declared.

No examples provided.

business_days_between ~59

Count South African business days between two dates (excludes the start date, includes the end date). (paid via Apify)

NameTypeReqDescription
fromstringyesDate as YYYY-MM-DD
tostringyesDate as YYYY-MM-DD

No output schema declared.

No examples provided.

days_until_next_holiday ~49

Find the next South African public holiday after a date and how many calendar days until it. Includes observed and once-off declared holidays.

NameTypeReqDescription
datestringyesDate as YYYY-MM-DD

No output schema declared.

No examples provided.

holidays_in_range ~61

List South African public holidays between two dates, including Sunday-to-Monday observed days and once-off declared holidays. (paid via Apify)

NameTypeReqDescription
fromstringyesDate as YYYY-MM-DD
tostringyesDate as YYYY-MM-DD

No output schema declared.

No examples provided.

is_business_day ~48

Check whether a date is a business day in South Africa (not a weekend or SA public holiday). Returns the reason if it isn't.

NameTypeReqDescription
datestringyesDate as YYYY-MM-DD

No output schema declared.

No examples provided.

next_sars_deadlines ~81

List the next SARS EMP201 (PAYE) and VAT201 due dates from a given date, adjusted for weekends and public holidays. Monthly VAT vendors; bi-monthly vendors use only their period-end months. (paid via Apify)

NameTypeReqDescription
countinteger–How many deadlines
fromstringyesDate as YYYY-MM-DD

No output schema declared.

No examples provided.

Install

How do I install the SA Business Calendar MCP server?

SA Business Calendar is a hosted endpoint at https://calendar.namka.cloud/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 · calendar.namka.cloud

# add to Claude Code
claude mcp add --transport http alimora83-sa-business-calendar-mcp 'https://calendar.namka.cloud/mcp'
Common questions

What is the SA Business Calendar MCP server?

SA Business Calendar is an MCP server listed in the public MCP registry as io.github.AliMora83/sa-business-calendar-mcp. South African business days, public holidays and SARS EMP201/VAT201 deadlines. This page covers its hosted endpoint (https://calendar.namka.cloud/mcp).

Is the SA Business Calendar MCP server safe to use?

SA Business Calendar scores 65 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 SA Business Calendar MCP server expose?

SA Business Calendar exposes 6 tools: is_business_day, add_business_days, business_days_between, holidays_in_range, days_until_next_holiday, next_sars_deadlines. Their descriptions and schemas cost roughly 377 tokens of context every time the server is loaded.

Does the SA Business Calendar MCP server require authentication?

No. We connected to SA Business Calendar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SA Business Calendar MCP server still maintained?

SA Business Calendar 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 SA Business Calendar MCP server?

VerifyMCP ran 11 checks on SA Business Calendar, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about SA Business Calendar: Authorization and 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.