# SA Business Calendar (remote · calendar.namka.cloud)

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

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

## Components

- remote · `ali-mora--sa-calendar-apify.apify.actor`: 34/100, [markdown](https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/ali-mora-sa-calendar-apify.md), [page](https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/ali-mora-sa-calendar-apify)
- remote · `calendar.namka.cloud`: 65/100 (this document), [markdown](https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/calendar.md), [page](https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/calendar)

## Channel facts

- Endpoint: `https://calendar.namka.cloud/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation 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 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 377 tokens (~62/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

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

### Claude

```bash
claude mcp add --transport http alimora83-sa-business-calendar-mcp 'https://calendar.namka.cloud/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "alimora83-sa-business-calendar-mcp": {
      "url": "https://calendar.namka.cloud/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alimora83-sa-business-calendar-mcp": {
      "type": "http",
      "url": "https://calendar.namka.cloud/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.alimora83-sa-business-calendar-mcp]
url = "https://calendar.namka.cloud/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alimora83-sa-business-calendar-mcp": {
      "type": "remote",
      "url": "https://calendar.namka.cloud/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alimora83-sa-business-calendar-mcp --url 'https://calendar.namka.cloud/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  alimora83-sa-business-calendar-mcp:
    url: "https://calendar.namka.cloud/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "alimora83-sa-business-calendar-mcp": {
      "Transport": "http",
      "Url": "https://calendar.namka.cloud/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add alimora83-sa-business-calendar-mcp -t streamable-http -u 'https://calendar.namka.cloud/mcp'
```

### Other

```json
{
  "mcpServers": {
    "alimora83-sa-business-calendar-mcp": {
      "type": "http",
      "url": "https://calendar.namka.cloud/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-21 (score 65, +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-11-19 (score 64, +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-11-17 (score 63, +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-11-15 (score 62, +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.

### 2026-11-14 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 61)

First indexed and scored.

## MCP tools (6)

### `is_business_day` (~48 tokens)

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.

Input parameters:

- `date` (string, required): Date as YYYY-MM-DD

### `add_business_days` (~79 tokens)

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)

Input parameters:

- `date` (string, required): Date as YYYY-MM-DD
- `days` (integer, required): Business days to add; negative to go back

### `business_days_between` (~59 tokens)

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

Input parameters:

- `from` (string, required): Date as YYYY-MM-DD
- `to` (string, required): Date as YYYY-MM-DD

### `holidays_in_range` (~61 tokens)

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

Input parameters:

- `from` (string, required): Date as YYYY-MM-DD
- `to` (string, required): Date as YYYY-MM-DD

### `days_until_next_holiday` (~49 tokens)

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

Input parameters:

- `date` (string, required): Date as YYYY-MM-DD

### `next_sars_deadlines` (~81 tokens)

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)

Input parameters:

- `count` (integer): How many deadlines
- `from` (string, required): Date as YYYY-MM-DD

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/calendar#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 62
- 2026-11-15: 62
- 2026-11-14: 61
- 2026-11-13: 61

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

## Links

- Remote endpoint: https://calendar.namka.cloud/mcp
- Repository: https://github.com/AliMora83/sa-business-calendar-mcp
- Website: https://apify.com/ali_mora/sa-calendar-apify
- Changelog RSS feed: https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/calendar.xml
- Changelog JSON feed: https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/calendar/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/calendar.json
- HTML version of this page: https://verifymcp.io/servers/alimora83-sa-business-calendar-mcp/calendar
