# SIMcloud (remote · simcloud.co.za)

South African MCP server for airtime, data, SMS, VAS, electricity, balance, and network lookup.

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

## Components

- remote · `simcloud.co.za`: 67/100 (this document), [markdown](https://verifymcp.io/servers/za-co-simcloud-simcloud/api-mcp-php.md), [page](https://verifymcp.io/servers/za-co-simcloud-simcloud/api-mcp-php)

## Channel facts

- Endpoint: `https://simcloud.co.za/api/mcp.php`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_sms).
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1560 tokens (~97/item across 16 items; 16 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**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http za-co-simcloud-simcloud https://simcloud.co.za/api/mcp.php
```

### Codex

```toml
[mcp_servers.za-co-simcloud-simcloud]
url = "https://simcloud.co.za/api/mcp.php"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "za-co-simcloud-simcloud": {
      "type": "remote",
      "url": "https://simcloud.co.za/api/mcp.php",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add za-co-simcloud-simcloud --url https://simcloud.co.za/api/mcp.php --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  za-co-simcloud-simcloud:
    url: "https://simcloud.co.za/api/mcp.php"
```

### Other

```json
{
  "mcpServers": {
    "za-co-simcloud-simcloud": {
      "type": "http",
      "url": "https://simcloud.co.za/api/mcp.php"
    }
  }
}
```

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-08-03 (score 67, +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-08-01 (score 66, +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-07-31 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1363 → 1560
- [functional] New tool “get_transaction_history”

### 2026-07-28 (score 64, +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-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (16)

### `get_wallet_balance` (~42 tokens)

Get wallet balance

Use this before a wallet-funded SIMcloud transaction or when the user asks for their available SIMcloud balance. Returns the authenticated account wallet balance and does not spend funds.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `get_transaction_history` (~174 tokens)

Get transaction history

Use this to retrieve read-only transaction history for the authenticated SIMcloud account across web, CSV, recurring and API airtime, data, SMS, VAS and electricity activity. Require a date range; optionally filter one or more services with a comma-separated type value. SMS is successful only after a delivery receipt.

Input parameters:

- `cursor` (string): Opaque cursor returned by the previous result. Keep the same date range and type filter.
- `date_from` (string, required): Inclusive start date in YYYY-MM-DD format, interpreted in Africa/Johannesburg time.
- `date_to` (string, required): Inclusive end date in YYYY-MM-DD format. The maximum range is 90 days.
- `limit` (integer)
- `type` (string): Optional comma-separated service filter: airtime, data, electricity, vas and sms.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `lookup_network` (~64 tokens)

Look up mobile network

Use this when the user needs to identify the South African mobile network for a number before sending airtime, data or SMS. The lookup is recorded in the authenticated account history.

Input parameters:

- `msisdn` (string, required): South African mobile number, for example 0821234567.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `send_sms` (~84 tokens)

Send SMS

Use this when an authenticated SIMcloud user asks to send a confirmed SMS to a South African recipient. Confirm the final recipient and message before calling. Sending is an irreversible external action and may spend wallet funds; do not automatically retry an ambiguous result.

Input parameters:

- `message` (string, required): SMS message body.
- `recipient` (string, required): Recipient number, for example +27821234567.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `get_sms_status` (~36 tokens)

Get SMS status

Use this after send_sms to fetch the delivery status of an authenticated account SMS by sms_id.

Input parameters:

- `sms_id` (integer, required)

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `create_airtime_order` (~181 tokens)

Send South African airtime

Use this when an authenticated SIMcloud user asks to send or recharge prepaid airtime to a South African mobile number on MTN, Vodacom, Cell C or Telkom. Confirm the MSISDN, network, rand amount and reference before calling. This spends wallet funds and queues an irreversible external transaction. Never automatically retry an ambiguous result. Duplicate same-MSISDN-and-amount requests inside 5 minutes return HTTP 409.

Input parameters:

- `amount` (number, required): Airtime amount in South African rand, from R2 to R999.
- `msisdn` (string, required): South African mobile number to recharge, for example 0821234567 or +27821234567.
- `network` (string, required): Supported South African airtime network name or SIMcloud internal code.
- `reference` (string, required): User or system reference for this airtime order.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `get_airtime_order` (~74 tokens)

Get airtime order

Use this after create_airtime_order, or after an ambiguous create result, to fetch the authenticated account airtime order by request_id or orderno.

Input parameters:

- `orderno` (string): SIMcloud platform order number returned during processing.
- `request_id` (integer): SIMcloud request identifier returned when the order was queued.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `create_data_order` (~162 tokens)

Create data order

Use this when an authenticated SIMcloud user asks to send a confirmed South African mobile data bundle. Call list_data_products first and use an available network and sell value. This spends wallet funds and queues an irreversible external transaction. Never automatically retry an ambiguous result. Duplicate same-MSISDN-and-amount requests inside 5 minutes return HTTP 409.

Input parameters:

- `amount` (number, required): Exact data bundle sell value returned by list_data_products.
- `msisdn` (string, required): South African mobile number to recharge, for example 0821234567 or +27821234567.
- `network` (string, required): Supported South African data network name or SIMcloud internal code returned by list_data_products.
- `reference` (string, required): User or system reference for this data order.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `list_data_products` (~63 tokens)

List data products

Use this before create_data_order to list the current SIMcloud data bundle products and exact sell values available for API ordering, optionally filtered by South African network.

Input parameters:

- `network` (string): Optional friendly network name or internal code, for example mtn or pd-mtn.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `get_data_order` (~71 tokens)

Get data order

Use this after create_data_order, or after an ambiguous create result, to fetch the authenticated account data order by request_id or orderno.

Input parameters:

- `orderno` (string): SIMcloud platform order number returned during processing.
- `request_id` (integer): SIMcloud request identifier returned when the order was queued.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `list_vas_products` (~31 tokens)

List VAS products

Use this before create_vas_order to list active SIMcloud VAS voucher products and their available denominations.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `create_vas_order` (~119 tokens)

Create VAS order

Use this when an authenticated SIMcloud user asks to buy a confirmed VAS voucher. Call list_vas_products first and use an available product and denomination. This spends wallet funds and queues an irreversible external transaction; do not automatically retry an ambiguous result.

Input parameters:

- `amount` (number, required)
- `product_id` (integer): SIMcloud VAS product ID. Required when voucher_type is not supplied.
- `reference` (string, required)
- `voucher_type` (string): Exact VAS voucher type or slug. Required when product_id is not supplied.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `get_vas_order` (~56 tokens)

Get VAS order

Use this after create_vas_order, or after an ambiguous create result, to fetch an authenticated account VAS order by order_id or transaction_id.

Input parameters:

- `order_id` (integer)
- `transaction_id` (string)

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `create_electricity_order` (~141 tokens)

Create electricity order

Use this when an authenticated SIMcloud user asks to buy prepaid electricity for a meter already confirmed with check_electricity_meter. Confirm the meter, rand amount, reference and SMS recipient before calling. This spends wallet funds and submits an irreversible external transaction; do not automatically retry an ambiguous result.

Input parameters:

- `amount` (number, required): Electricity purchase amount in South African rand, from R50 to R1000.
- `client_reference` (string, required): User or system reference for this electricity order.
- `meter_number` (string, required): Prepaid electricity meter number previously checked with check_electricity_meter.
- `recipient` (string, required): Recipient mobile number for voucher notifications.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `check_electricity_meter` (~54 tokens)

Check electricity meter

Use this before create_electricity_order to check whether a prepaid electricity meter is supported. This does not buy electricity or spend wallet funds.

Input parameters:

- `meter_number` (string, required): Prepaid electricity meter number to validate.

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

### `get_electricity_order` (~70 tokens)

Get electricity order

Use this after create_electricity_order, or after an ambiguous create result, to fetch an authenticated account electricity order by order_id, client_reference or order_reference_id.

Input parameters:

- `client_reference` (string)
- `order_id` (integer)
- `order_reference_id` (string)

Output parameters:

- `data`: Decoded SIMcloud API response body.
- `ok` (boolean): Whether the proxied SIMcloud API request returned a 2xx response.
- `status` (integer): HTTP status returned by the SIMcloud API, or 0 when no HTTP response was received.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/za-co-simcloud-simcloud/api-mcp-php#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://simcloud.co.za/api/mcp.php
- Repository: https://github.com/ErikThiart/simcloud
- Website: https://simcloud.co.za/api/ai.html
- Changelog RSS feed: https://verifymcp.io/servers/za-co-simcloud-simcloud/api-mcp-php/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/za-co-simcloud-simcloud/api-mcp-php/changelog.json
- HTML version of this page: https://verifymcp.io/servers/za-co-simcloud-simcloud/api-mcp-php