io.usefulapi/intakeq
REMOTE · INTAKEQ.USEFULAPI.IO · SCANNED OCT 3
Search clients, appointments, intakes, notes and invoices in IntakeQ, and book or cancel visits.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · intakeq.usefulapi.io
claude mcp add --transport http io-usefulapi-intakeq 'https://intakeq.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-intakeq": {
"url": "https://intakeq.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-intakeq": {
"type": "http",
"url": "https://intakeq.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-intakeq] url = "https://intakeq.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-intakeq": {
"type": "remote",
"url": "https://intakeq.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-intakeq --url 'https://intakeq.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-intakeq:
url: "https://intakeq.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-intakeq": {
"Transport": "http",
"Url": "https://intakeq.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-intakeq -t streamable-http -u 'https://intakeq.usefulapi.io/mcp'
{
"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.
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.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +4
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
First indexed and scored.
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 3 Oct 2026 · Probed https://intakeq.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 intakeq.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://intakeq.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://intakeq.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://intakeq.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://intakeq.usefulapi.io/mcp |
| Authorisation server | https://intakeq.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://intakeq.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://intakeq.usefulapi.io/mcp | HTTPS enforced | 301 | https://intakeq.usefulapi.io/mcp |
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 →
intakeq_add_client_tag Tag a client ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | The client's numeric id. |
| tag | string | yes | The tag text. |
No output schema declared.
No examples provided.
intakeq_cancel_appointment Cancel an appointment ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | string | yes | The appointment's id. |
| reason | string | – | Why it was canceled. |
No output schema declared.
No examples provided.
intakeq_create_appointment Create an appointment ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ClientId | integer | yes | The client's numeric id. |
| LocationId | string | yes | The location's id. |
| PractitionerId | string | yes | The practitioner's id. |
| ReminderType | string | yes | Reminder channel: Sms, Email, Voice or OptOut. |
| SendClientEmailNotification | boolean | yes | Email the client (only allowed when Status=Confirmed). |
| ServiceId | string | yes | The service's id. |
| Status | string | yes | Initial status. |
| UtcDateTime | integer | yes | Start time as a UTC Unix timestamp in ms. |
No output schema declared.
No examples provided.
intakeq_get_appointment Get one appointment ~60
Fetch one appointment: client, practitioner, service, location, start/end, status, price, invoice, telehealth link and cancellation details. IntakeQ: GET /appointments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | string | yes | The appointment's id. |
No output schema declared.
No examples provided.
intakeq_get_booking_settings Get booking settings ~44
List the scheduler's locations, services (with duration and price) and practitioners — the ids you need to create an appointment. IntakeQ: GET /appointments/settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
intakeq_get_client_diagnoses Get a client's diagnoses ~67
List the diagnoses recorded for one client: code, description, start/end date and the treatment note they came from. IntakeQ: GET /client/{clientId}/diagnoses.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | The client's numeric id (ClientId / ClientNumber). |
No output schema declared.
No examples provided.
intakeq_get_intake Get a full intake form ~53
Fetch one intake questionnaire with every question and answer, its consent forms and linked appointment. IntakeQ: GET /intakes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| intake_id | string | yes | The intake's id (a GUID). |
No output schema declared.
No examples provided.
intakeq_get_invoice Get one invoice ~50
Fetch one invoice: line items, taxes, discounts, payments, totals and amount due. IntakeQ: GET /invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | The invoice's id. |
No output schema declared.
No examples provided.
intakeq_get_note Get a full treatment note ~48
Fetch one treatment note with every question and answer and its linked appointment. IntakeQ: GET /notes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | string | yes | The note's id (a GUID). |
No output schema declared.
No examples provided.
intakeq_list_appointments List appointments ~178
Query appointments by client name/email, date range, status, practitioner or last-modified date. Max 100 per page. IntakeQ: GET /appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
intakeq_list_clients Search clients ~285
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
intakeq_list_intakes List intake forms ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
intakeq_list_invoices List invoices ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
intakeq_list_notes List treatment notes ~177
Query treatment note summaries by client, lock status, date range or last-updated date. Max 100 per page. IntakeQ: GET /notes/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
intakeq_list_practitioners List practitioners ~39
List the practitioners in the account (id, name, email, external id). IntakeQ: GET /practitioners.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
intakeq_list_questionnaires List questionnaire templates ~45
List the intake questionnaire templates in the account (id, name, archived, anonymous) — the ids you need to send one. IntakeQ: GET /questionnaires.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
intakeq_save_client Create or update a client ~472
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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 | – | – |
No output schema declared.
No examples provided.
intakeq_send_questionnaire Send an intake questionnaire ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The questionnaire template id (intakeq_list_questionnaires). |
No output schema declared.
No examples provided.
intakeq_update_appointment Update or reschedule an appointment ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| Id | string | yes | 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 | yes | Start time as a UTC Unix timestamp in ms (required even if unchanged). |
No output schema declared.
No examples provided.
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 76 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 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.