# io.usefulapi/intakeq (remote · intakeq.usefulapi.io)

Search clients, appointments, intakes, notes and invoices in IntakeQ, and book or cancel visits.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

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

## Channel facts

- Endpoint: `https://intakeq.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-04.

- **Endpoint Security**: 89/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 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.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2605 tokens (~137/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 19 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 io.usefulapi/intakeq MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-intakeq": {
      "type": "http",
      "url": "https://intakeq.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-04 (score 77, +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-10-02 (score 76, +1)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 75, +4)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 71, +53)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 100
- [functional] First check of Tool coverage: 73

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (19)

### `intakeq_list_clients` (~285 tokens)

Search clients

Search the practice's clients (patients) by name, email or client number, by created/updated date range, by external id, or by a custom field. Without include_profile it returns Name, Email, Phone and ClientNumber; with include_profile=true it returns the full profile (address, insurance, tags, custom fields, linked clients). Max 100 per page. IntakeQ: GET /clients.

Input parameters:

- `custom_fields` (object): Match on custom fields: { "<FieldId>": "<value>" } (sent as custom.<FieldId>=<value>).
- `date_created_end` (string): Created on or before (yyyy-MM-dd).
- `date_created_start` (string): Created on or after (yyyy-MM-dd).
- `date_updated_end` (string): Updated on or before (yyyy-MM-dd).
- `date_updated_start` (string): Updated on or after (yyyy-MM-dd).
- `deleted_only` (boolean): true = only clients deleted in the last 10 days.
- `external_client_id` (string): Look up by your external client id.
- `include_profile` (boolean): true = return the full client profile.
- `page` (integer): Page number (1, 2, ...). Each page holds at most 100 records.
- `search` (string): Client name, email, or numeric client id.

### `intakeq_get_client_diagnoses` (~67 tokens)

Get a client's diagnoses

List the diagnoses recorded for one client: code, description, start/end date and the treatment note they came from. IntakeQ: GET /client/{clientId}/diagnoses.

Input parameters:

- `client_id` (integer, required): The client's numeric id (ClientId / ClientNumber).

### `intakeq_list_appointments` (~178 tokens)

List appointments

Query appointments by client name/email, date range, status, practitioner or last-modified date. Max 100 per page. IntakeQ: GET /appointments.

Input parameters:

- `client` (string): Client name or email (partial matches).
- `deleted_only` (boolean): true = only appointments deleted in the last 10 days.
- `end_date` (string): Appointments on or before (yyyy-MM-dd).
- `page` (integer): Page number (1, 2, ...). Each page holds at most 100 records.
- `practitioner_email` (string): Only this practitioner's appointments.
- `start_date` (string): Appointments on or after (yyyy-MM-dd).
- `status` (string): Only appointments in this status.
- `updated_since` (string): Only appointments modified after this date (yyyy-MM-dd).

### `intakeq_get_appointment` (~60 tokens)

Get one appointment

Fetch one appointment: client, practitioner, service, location, start/end, status, price, invoice, telehealth link and cancellation details. IntakeQ: GET /appointments/{id}.

Input parameters:

- `appointment_id` (string, required): The appointment's id.

### `intakeq_get_booking_settings` (~44 tokens)

Get booking settings

List the scheduler's locations, services (with duration and price) and practitioners — the ids you need to create an appointment. IntakeQ: GET /appointments/settings.

### `intakeq_list_intakes` (~223 tokens)

List intake forms

Query submitted intake questionnaires (summaries: client, status, questionnaire, practitioner, dates). By default only completed forms; set all=true for every status (Sent, Partial, Completed, Offline). Max 100 per page. IntakeQ: GET /intakes/summary.

Input parameters:

- `all` (boolean): true = return intakes of every status, not only completed.
- `client` (string): Client name or email (partial matches).
- `client_id` (integer): Only this client's intakes.
- `deleted_only` (boolean): true = only intakes deleted in the last 10 days.
- `end_date` (string): On or before (yyyy-MM-dd).
- `external_client_id` (string): Only intakes for this external client id.
- `page` (integer): Page number (1, 2, ...). Each page holds at most 100 records.
- `start_date` (string): On or after (yyyy-MM-dd).
- `updated_since` (string): Only intakes updated after this date (yyyy-MM-dd).

### `intakeq_get_intake` (~53 tokens)

Get a full intake form

Fetch one intake questionnaire with every question and answer, its consent forms and linked appointment. IntakeQ: GET /intakes/{id}.

Input parameters:

- `intake_id` (string, required): The intake's id (a GUID).

### `intakeq_list_questionnaires` (~45 tokens)

List questionnaire templates

List the intake questionnaire templates in the account (id, name, archived, anonymous) — the ids you need to send one. IntakeQ: GET /questionnaires.

### `intakeq_list_practitioners` (~39 tokens)

List practitioners

List the practitioners in the account (id, name, email, external id). IntakeQ: GET /practitioners.

### `intakeq_list_notes` (~177 tokens)

List treatment notes

Query treatment note summaries by client, lock status, date range or last-updated date. Max 100 per page. IntakeQ: GET /notes/summary.

Input parameters:

- `client` (string): Client name or email (partial matches).
- `client_id` (integer): Only this client's notes.
- `deleted_only` (boolean): true = only notes deleted in the last 10 days.
- `end_date` (string): On or before (yyyy-MM-dd).
- `page` (integer): Page number (1, 2, ...). Each page holds at most 100 records.
- `start_date` (string): On or after (yyyy-MM-dd).
- `status`: 1 = locked notes, 2 = unlocked notes.
- `updated_since` (string): Only notes updated after this date (yyyy-MM-dd).

### `intakeq_get_note` (~48 tokens)

Get a full treatment note

Fetch one treatment note with every question and answer and its linked appointment. IntakeQ: GET /notes/{id}.

Input parameters:

- `note_id` (string, required): The note's id (a GUID).

### `intakeq_list_invoices` (~191 tokens)

List invoices

Query invoices by client, issue date range, status, practitioner or last-updated range. Each invoice includes items, payments and amounts due/paid. Max 100 per page. IntakeQ: GET /invoices.

Input parameters:

- `client_id` (integer): Only this client's invoices (numeric client id).
- `end_date` (string): Invoices on or before (yyyy-MM-dd).
- `last_updated_end_date` (string): Changed on or before (yyyy-MM-dd).
- `last_updated_start_date` (string): Changed on or after (yyyy-MM-dd).
- `page` (integer): Page number (1, 2, ...). Each page holds at most 100 records.
- `practitioner_email` (string): Only this practitioner's invoices.
- `start_date` (string): Invoices on or after (yyyy-MM-dd).
- `status` (string): Only invoices in this status.

### `intakeq_get_invoice` (~50 tokens)

Get one invoice

Fetch one invoice: line items, taxes, discounts, payments, totals and amount due. IntakeQ: GET /invoices/{id}.

Input parameters:

- `invoice_id` (string, required): The invoice's id.

### `intakeq_save_client` (~472 tokens)

Create or update a client

Create a client, or update one. With ClientId the existing client is updated. WITHOUT ClientId IntakeQ still tries to match an existing client by first name + email (or first name + phone) and updates that one instead of creating a duplicate. For updates, fetch the full profile first (intakeq_list_clients with include_profile=true) and send it back with your changes, so no field is unintentionally cleared. Field names are IntakeQ's own. Dates are Unix timestamps in milliseconds. IntakeQ: POST /clients.

Input parameters:

- `AdditionalInformation` (string)
- `Address` (string): Full address, or send the components below instead.
- `Archived` (boolean)
- `City` (string)
- `ClientId` (integer): Update this existing client.
- `Country` (string)
- `CustomFields` (array): Custom field values (FieldId + Value).
- `DateOfBirth` (integer): Unix timestamp in ms.
- `Email` (string)
- `ExternalClientId` (string)
- `FirstName` (string)
- `Gender` (string)
- `HomePhone` (string)
- `LastName` (string)
- `MaritalStatus` (string)
- `MiddleName` (string)
- `MobilePhone` (string)
- `Name` (string): Full name.
- `Phone` (string)
- `PostalCode` (string)
- `PractitionerId` (string): Assign to this practitioner.
- `PrimaryInsuranceCompany` (string)
- `PrimaryInsuranceGroupNumber` (string)
- `PrimaryInsuranceHolderDateOfBirth` (integer): Unix timestamp in ms.
- `PrimaryInsuranceHolderName` (string)
- `PrimaryInsurancePolicyNumber` (string)
- `PrimaryInsuranceRelationship` (string)
- `SecondaryInsuranceCompany` (string)
- `SecondaryInsuranceGroupNumber` (string)
- `SecondaryInsuranceHolderDateOfBirth` (integer): Unix timestamp in ms.
- `SecondaryInsuranceHolderName` (string)
- `SecondaryInsurancePolicyNumber` (string)
- `SecondaryInsuranceRelationship` (string)
- `StateShort` (string)
- `StreetAddress` (string)
- `UnitNumber` (string)
- `WorkPhone` (string)

### `intakeq_add_client_tag` (~69 tokens)

Tag a client

Add a tag to a client. The tag is created if it does not exist; adding one the client already has is a no-op. IntakeQ: POST /clientTags.

Input parameters:

- `client_id` (integer, required): The client's numeric id.
- `tag` (string, required): The tag text.

### `intakeq_create_appointment` (~189 tokens)

Create an appointment

Book an appointment in the PracticeQ scheduler. Get PractitionerId, ServiceId and LocationId from intakeq_get_booking_settings. All fields are required by IntakeQ. Status must be Confirmed or WaitingConfirmation; SendClientEmailNotification may be true only when Status is Confirmed. IntakeQ: POST /appointments.

Input parameters:

- `ClientId` (integer, required): The client's numeric id.
- `LocationId` (string, required): The location's id.
- `PractitionerId` (string, required): The practitioner's id.
- `ReminderType` (string, required): Reminder channel: Sms, Email, Voice or OptOut.
- `SendClientEmailNotification` (boolean, required): Email the client (only allowed when Status=Confirmed).
- `ServiceId` (string, required): The service's id.
- `Status` (string, required): Initial status.
- `UtcDateTime` (integer, required): Start time as a UTC Unix timestamp in ms.

### `intakeq_update_appointment` (~169 tokens)

Update or reschedule an appointment

Change an appointment's time, service, location, status or reminder type. Id and UtcDateTime are required (send the current time to keep it); include only the other fields you are changing. The client and practitioner cannot be changed, and a Confirmed appointment cannot go back to WaitingConfirmation. IntakeQ: PUT /appointments.

Input parameters:

- `Id` (string, required): The appointment's id.
- `LocationId` (string): New location id.
- `ReminderType` (string)
- `SendClientEmailNotification` (boolean): Email the client about the change.
- `ServiceId` (string): New service id.
- `Status` (string): New status.
- `UtcDateTime` (integer, required): Start time as a UTC Unix timestamp in ms (required even if unchanged).

### `intakeq_cancel_appointment` (~73 tokens)

Cancel an appointment

Cancel an appointment, with an optional reason. This changes the client's booking and cannot be undone through the API — book a new appointment to replace it. IntakeQ: POST /appointments/cancellation.

Input parameters:

- `appointment_id` (string, required): The appointment's id.
- `reason` (string): Why it was canceled.

### `intakeq_send_questionnaire` (~173 tokens)

Send an intake questionnaire

Send an intake questionnaire to a client by email or SMS. This MESSAGES THE CLIENT. Identify the client by ClientId, or by ClientName plus ClientEmail and/or ClientPhone (omit ClientEmail to force SMS). PractitionerId is optional. Returns the new intake. IntakeQ: POST /intakes/send.

Input parameters:

- `ClientEmail` (string): Email delivery address.
- `ClientId` (integer): An existing client's numeric id.
- `ClientName` (string): First and last name, if not using ClientId.
- `ClientPhone` (string): SMS delivery number.
- `ExternalClientId` (string): Partners only.
- `PractitionerId` (string): Practitioner to associate; defaults to the client's.
- `QuestionnaireId` (string, required): The questionnaire template id (intakeq_list_questionnaires).

## Diagnostics

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

## Score history

- 2026-10-04: 77
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 71
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/intakeq MCP server?

io.usefulapi/intakeq is an MCP server listed in the public MCP registry as io.usefulapi/intakeq. Search clients, appointments, intakes, notes and invoices in IntakeQ, and book or cancel visits. This page covers its hosted endpoint (https://intakeq.usefulapi.io/mcp).

### Is the io.usefulapi/intakeq MCP server safe to use?

io.usefulapi/intakeq scores 77 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 io.usefulapi/intakeq MCP server expose?

io.usefulapi/intakeq exposes 19 tools: intakeq_list_clients, intakeq_get_client_diagnoses, intakeq_list_appointments, intakeq_get_appointment, intakeq_get_booking_settings, and 14 more. Their descriptions and schemas cost roughly 2,605 tokens of context every time the server is loaded.

### Does the io.usefulapi/intakeq MCP server require authentication?

Yes. io.usefulapi/intakeq 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 io.usefulapi/intakeq MCP server still maintained?

io.usefulapi/intakeq is still listed as active in the MCP registry. We last reached this channel on 4 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://intakeq.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-intakeq/intakeq.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-intakeq/intakeq.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-intakeq/intakeq