# Nookal MCP by usefulapi (remote · nookal.usefulapi.io)

Read Nookal locations, practitioners, availability, appointments, clients, cases and invoices.

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

## Components

- remote · `nookal.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-nookal/nookal.md), [page](https://verifymcp.io/servers/io-usefulapi-nookal/nookal)

## Channel facts

- Endpoint: `https://nookal.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.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-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2448 tokens (~222/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Nookal MCP by usefulapi server?

Nookal MCP by usefulapi is a hosted endpoint at https://nookal.usefulapi.io/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 io-usefulapi-nookal 'https://nookal.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-nookal": {
      "url": "https://nookal.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-nookal": {
      "type": "http",
      "url": "https://nookal.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-nookal]
url = "https://nookal.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-nookal": {
      "type": "remote",
      "url": "https://nookal.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-nookal --url 'https://nookal.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-nookal:
    url: "https://nookal.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-nookal": {
      "Transport": "http",
      "Url": "https://nookal.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-nookal -t streamable-http -u 'https://nookal.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-nookal": {
      "type": "http",
      "url": "https://nookal.usefulapi.io/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-10-17 (score 65, +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.

### 2026-10-15 (score 64, +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.

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.4.0 → 1.5.0

### 2026-10-13 (score 61, +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.

### 2026-10-12 (score 60, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 59)

First indexed and scored.

## MCP tools (11)

### `nookal_list_locations` (~127 tokens)

List locations

List the clinic's locations (id, name, address, time zone, active). Location ids are needed by most other tools. Only the locations your API client was granted are returned. Nookal GraphQL: locations.

Input parameters:

- `active` (boolean): true = only active locations, false = only inactive.
- `location_ids` (array): Only these locations (numeric Nookal ids, up to 100).
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).

### `nookal_list_staff` (~224 tokens)

List practitioners and staff

List staff members and practitioners (id, name, title, speciality, email, location ids, whether they are a provider / bookable online / active). Use the staff ids as provider_ids in list_appointments and staff_ids in get_availability. Nookal GraphQL: staff.

Input parameters:

- `active` (boolean): true = only active staff, false = only inactive (Nookal status 1/0).
- `location_ids` (array): Only these locations' staff (numeric Nookal ids, up to 100).
- `online_bookings` (boolean): true = only staff bookable online, false = only staff not bookable online.
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).
- `providers_only` (boolean): true = only clinical providers (practitioners), false = only non-providers.
- `staff_ids` (array): Only these staff members (numeric Nookal ids, up to 100).

### `nookal_list_services` (~156 tokens)

List services (appointment types)

List the appointment types / services offered (id, name, category, duration in minutes, price, location, online-booking settings). Use a service id in get_availability. Nookal GraphQL: services.

Input parameters:

- `location_ids` (array): Only these locations' services (numeric Nookal ids, up to 100).
- `online_bookings` (boolean): true = only services bookable online, false = only diary-only services.
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).
- `service_ids` (array): Only these services (numeric Nookal ids, up to 100).

### `nookal_list_classes` (~153 tokens)

List class types

List the class types offered (id, name, category, duration, price, location, online-booking settings) — the class definitions, not individual sessions. Nookal GraphQL: classes.

Input parameters:

- `class_ids` (array): Only these class types (numeric Nookal ids, up to 100).
- `location_ids` (array): Only these locations' classes (numeric Nookal ids, up to 100).
- `online_bookings` (boolean): true = only classes bookable online, false = only diary-only classes.
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).

### `nookal_get_availability` (~203 tokens)

Get appointment availability

Get the free appointment slots per date between two dates (max 60 days, Nookal's limit), optionally for given locations, practitioners and a service. Each slot has its date, start time (24h, clinic local time), provider id and location id. Read-only: it does not book anything. Nookal GraphQL: availabilities.

Input parameters:

- `date_from` (string, required): First date, YYYY-MM-DD.
- `date_to` (string, required): Last date, YYYY-MM-DD (at most 60 days after date_from).
- `location_ids` (array): Only these locations (numeric Nookal ids, up to 100).
- `service_id` (integer): Only slots for this service / appointment type id (from list_services).
- `slot_duration` (integer): Override the slot length in minutes.
- `staff_ids` (array): Only these practitioners (staff ids) (numeric Nookal ids, up to 100).

### `nookal_list_appointments` (~354 tokens)

List appointments

List appointments (date, start/end time, status, type, client, practitioner, case, location, arrived / did-not-arrive flags, notes), filtered by date range, location, client, practitioner, type and status. Dates are clinic local. Nookal GraphQL: appointments.

Input parameters:

- `appointment_ids` (array): Only these appointments (numeric Nookal ids, up to 100).
- `appt_statuses` (array): Statuses as Nookal names them, e.g. ["Completed"], ["Cancelled"], ["DNA"] (did not arrive), ["Pending"].
- `appt_types` (array): Appointment kinds, e.g. ["Consultation"] or ["Class"].
- `client_ids` (array): Only these clients (patients) (numeric Nookal ids, up to 100).
- `date_from` (string): Appointments on or after this date, YYYY-MM-DD.
- `date_to` (string): Appointments on or before this date, YYYY-MM-DD.
- `location_ids` (array): Only these locations (numeric Nookal ids, up to 100).
- `modified_from` (string): Only appointments created/updated after this (YYYY-MM-DD or YYYY-MM-DD HH:MM:SS).
- `modified_to` (string): Only appointments created/updated before this (YYYY-MM-DD or YYYY-MM-DD HH:MM:SS).
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).
- `provider_ids` (array): Only these practitioners (staff ids) (numeric Nookal ids, up to 100).

### `nookal_search_clients` (~330 tokens)

Search clients (patients)

Find clients (patients) by name, date of birth, mobile, email or id. Returns id, name, date of birth, location, active/deceased flags and contact details. With partial_match, names match on their first letters (e.g. 'Sm' finds Smith). Nookal GraphQL: clients.

Input parameters:

- `active` (boolean): true = only active clients, false = only inactive.
- `client_ids` (array): Only these clients (numeric Nookal ids, up to 100).
- `date_of_birth` (string): Date of birth, YYYY-MM-DD.
- `deceased` (boolean): true = only deceased clients, false = only living clients.
- `email` (string): Email address.
- `first_name` (string): First name (exact, or its first letters with partial_match).
- `last_name` (string): Last name (exact, or its first letters with partial_match).
- `location_ids` (array): Only these locations' clients (numeric Nookal ids, up to 100).
- `mobile` (string): Mobile number, digits only with no spaces.
- `modified_from` (string): Only clients created/updated after this (YYYY-MM-DD or YYYY-MM-DD HH:MM:SS).
- `online_quick_code` (string): The client's online quick code.
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).
- `partial_match` (boolean): true = match names that start with the given letters.

### `nookal_get_client` (~122 tokens)

Get a client (patient)

Get one client (patient) by id: name, date of birth, contact details, addresses, alerts, allergies, notes, occupation, referring doctor and their treatment cases; optionally a summary of their invoices (totals and balances). Health-fund, pension and online-booking codes are not returned. Nookal GraphQL: clients.

Input parameters:

- `client_id` (integer, required): Nookal client id (from search_clients).
- `include_invoices` (boolean): true = also list the client's invoices (number, date, total, paid, balance).

### `nookal_list_cases` (~158 tokens)

List treatment cases

List treatment cases (id, client, title, start and referral dates, referrer, primary practitioner, notes), filtered by client, case or practitioner. Nookal GraphQL: cases.

Input parameters:

- `case_ids` (array): Only these cases (numeric Nookal ids, up to 100).
- `client_ids` (array): Only these clients' cases (numeric Nookal ids, up to 100).
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).
- `primary_provider_ids` (array): Only these primary practitioners' cases (staff ids) (numeric Nookal ids, up to 100).

### `nookal_list_invoices` (~248 tokens)

List invoices

List invoices with their line items and payments (number, client, case, location, practitioner, date, subtotal, tax, total, paid, balance), filtered by location, invoice id or creation date. For one client's invoices use get_client with include_invoices. Nookal GraphQL: invoices.

Input parameters:

- `created_from` (string): Invoices created on/after this (YYYY-MM-DD = from 00:00:00, or YYYY-MM-DD HH:MM:SS; clinic local time).
- `created_to` (string): Invoices created on/before this (YYYY-MM-DD = until 23:59:59, or YYYY-MM-DD HH:MM:SS; clinic local time).
- `invoice_ids` (array): Only these invoices (numeric Nookal ids, up to 100).
- `location_ids` (array): Only these locations' invoices (numeric Nookal ids, up to 100).
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).
- `voided_only` (boolean): true = only voided invoices.

### `nookal_list_payments` (~163 tokens)

List invoice payments

List payments received against invoices (method, amount, date, reference, invoice, client, location), filtered by invoice or payment date. Nookal GraphQL: payments.

Input parameters:

- `date_from` (string): Payments on/after this (YYYY-MM-DD or YYYY-MM-DD HH:MM:SS, clinic local time).
- `date_to` (string): Payments on/before this (YYYY-MM-DD or YYYY-MM-DD HH:MM:SS, clinic local time).
- `invoice_ids` (array): Only these invoices' payments (numeric Nookal ids, up to 100).
- `page` (integer): Page number (default 1).
- `page_length` (integer): Items per page, 1-100 (default 50).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-nookal/nookal#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 60
- 2026-10-10: 59

## Common questions

### What is the Nookal MCP by usefulapi server?

Nookal MCP by usefulapi is listed in the public MCP registry as io.usefulapi/nookal. Read Nookal locations, practitioners, availability, appointments, clients, cases and invoices. This page covers its hosted endpoint (https://nookal.usefulapi.io/mcp).

### Is the Nookal MCP by usefulapi server safe to use?

Nookal MCP by usefulapi 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 Nookal MCP by usefulapi server expose?

Nookal MCP by usefulapi exposes 11 tools: nookal_list_locations, nookal_list_staff, nookal_list_services, nookal_list_classes, nookal_get_availability, and 6 more. Their descriptions and schemas cost roughly 2,238 tokens of context every time the server is loaded.

### Does the Nookal MCP by usefulapi server require authentication?

Yes. Nookal MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Nookal MCP by usefulapi server still maintained?

Nookal MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://nookal.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/nookal/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-nookal/nookal.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-nookal/nookal.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-nookal/nookal