Skip to content

IntakeQ MCP by usefulapi

io.usefulapi/intakequsefulapi.iostreamable-httpv1.40.4Scanned

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

19 tools: 6 can delete or cancel things and 13 only read.

Tools: 6 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 6
  • Reads text others write · 4
  • Can send data out · 1
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the IntakeQ MCP by usefulapi can do

The IntakeQ MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (6 tools: intakeq_save_client, intakeq_add_client_tag, intakeq_create_appointment, intakeq_update_appointment and 2 more). 13 tools only read.

6 tools read private data (intakeq_list_clients, intakeq_get_client_diagnoses, intakeq_list_appointments and 3 more); 4 tools bring in text other people can write (intakeq_list_clients, intakeq_list_appointments, intakeq_list_practitioners and 1 more); 1 tool can send data out of your system (intakeq_send_questionnaire). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

19 tools

Deletes or cancels 6Claude Code: deny
  • intakeq_add_client_tagAdd a tag to a client.No findings

    Why it is in this group

    • The name "intakeq_add_client_tag" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Tag a client
    • destructiveHint: true
  • intakeq_cancel_appointmentCancel an appointment, with an optional reason.No findings

    Why it is in this group

    • The name "intakeq_cancel_appointment" says "cancel": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Cancel an appointment
    • destructiveHint: true
  • intakeq_create_appointmentBook an appointment in the PracticeQ scheduler.No findings

    Why it is in this group

    • The name "intakeq_create_appointment" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create an appointment
    • destructiveHint: true
  • intakeq_save_clientCreate a client, or update one.No findings

    Why it is in this group

    • The name "intakeq_save_client" says "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create or update a client
    • destructiveHint: true
  • intakeq_send_questionnaireSend an intake questionnaire to a client by email or SMS.Can send data outNo findings

    Why it is in this group

    • The name "intakeq_send_questionnaire" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "intakeq_send_questionnaire" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send an intake questionnaire
    • destructiveHint: true
  • intakeq_update_appointmentChange an appointment's time, service, location, status or reminder type.No findings

    Why it is in this group

    • The name "intakeq_update_appointment" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update or reschedule an appointment
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • intakeq_get_appointmentFetch one appointment: client, practitioner, service, location, start/end, status, price, invoice, telehealth link and cancellation details.No findings

    Why it is in this group

    • The name "intakeq_get_appointment" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one appointment: client, practitioner, service, location, start/end, status, price, invoice, telehealth link and cancellation details. IntakeQ: GET /appointments/{id}.

    Annotations the server declares

    • title: Get one appointment
    • readOnlyHint: true
  • intakeq_get_booking_settingsList the scheduler's locations, services (with duration and price) and practitioners — the ids you need to create an appointment.No findings

    Why it is in this group

    • The name "intakeq_get_booking_settings" says "get": a word for reading.
    Description, as the server wrote it
    List the scheduler's locations, services (with duration and price) and practitioners — the ids you need to create an appointment. IntakeQ: GET /appointments/settings.

    Annotations the server declares

    • title: Get booking settings
    • readOnlyHint: true
  • intakeq_get_client_diagnosesList the diagnoses recorded for one client: code, description, start/end date and the treatment note they came from.Reads private dataNo findings

    Why it is in this group

    • The name "intakeq_get_client_diagnoses" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    List the diagnoses recorded for one client: code, description, start/end date and the treatment note they came from. IntakeQ: GET /client/{clientId}/diagnoses.

    Annotations the server declares

    • title: Get a client's diagnoses
    • readOnlyHint: true
  • intakeq_get_intakeFetch one intake questionnaire with every question and answer, its consent forms and linked appointment.No findings

    Why it is in this group

    • The name "intakeq_get_intake" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one intake questionnaire with every question and answer, its consent forms and linked appointment. IntakeQ: GET /intakes/{id}.

    Annotations the server declares

    • title: Get a full intake form
    • readOnlyHint: true
  • intakeq_get_invoiceFetch one invoice: line items, taxes, discounts, payments, totals and amount due.No findings

    Why it is in this group

    • The name "intakeq_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one invoice: line items, taxes, discounts, payments, totals and amount due. IntakeQ: GET /invoices/{id}.

    Annotations the server declares

    • title: Get one invoice
    • readOnlyHint: true
  • intakeq_get_noteFetch one treatment note with every question and answer and its linked appointment.Reads private dataNo findings

    Why it is in this group

    • The name "intakeq_get_note" says "get": a word for reading.

    What it can reach

    • private-dataThe name "intakeq_get_note" says "get" and "note": it reads notes.
    • private-dataThe description's first sentence says "fetch" and "note": it reads notes.
    Description, as the server wrote it
    Fetch one treatment note with every question and answer and its linked appointment. IntakeQ: GET /notes/{id}.

    Annotations the server declares

    • title: Get a full treatment note
    • readOnlyHint: true
  • intakeq_list_appointmentsQuery appointments by client name/email, date range, status, practitioner or last-modified date.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "intakeq_list_appointments" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "query" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "query" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Query appointments by client name/email, date range, status, practitioner or last-modified date. Max 100 per page. IntakeQ: GET /appointments.

    Annotations the server declares

    • title: List appointments
    • readOnlyHint: true
  • intakeq_list_clientsSearch the practice's clients (patients) by name, email or client number, by created/updated date range, by external id, or by a custom field.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "intakeq_list_clients" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "search" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search clients
    • readOnlyHint: true
  • intakeq_list_intakesQuery submitted intake questionnaires (summaries: client, status, questionnaire, practitioner, dates).No findings

    Why it is in this group

    • The name "intakeq_list_intakes" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List intake forms
    • readOnlyHint: true
  • intakeq_list_invoicesQuery invoices by client, issue date range, status, practitioner or last-updated range.Reads text others writeNo findings

    Why it is in this group

    • The name "intakeq_list_invoices" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "query" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • intakeq_list_notesQuery treatment note summaries by client, lock status, date range or last-updated date.Reads private dataNo findings

    Why it is in this group

    • The name "intakeq_list_notes" says "list": a word for reading.

    What it can reach

    • private-dataThe name "intakeq_list_notes" says "list" and "note": it reads notes.
    • private-dataThe description's first sentence says "query" and "note": it reads notes.
    Description, as the server wrote it
    Query treatment note summaries by client, lock status, date range or last-updated date. Max 100 per page. IntakeQ: GET /notes/summary.

    Annotations the server declares

    • title: List treatment notes
    • readOnlyHint: true
  • intakeq_list_practitionersList the practitioners in the account (id, name, email, external id).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "intakeq_list_practitioners" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List the practitioners in the account (id, name, email, external id). IntakeQ: GET /practitioners.

    Annotations the server declares

    • title: List practitioners
    • readOnlyHint: true
  • intakeq_list_questionnairesList the intake questionnaire templates in the account (id, name, archived, anonymous) — the ids you need to send one.No findings

    Why it is in this group

    • The name "intakeq_list_questionnaires" says "list": a word for reading.
    Description, as the server wrote it
    List the intake questionnaire templates in the account (id, name, archived, anonymous) — the ids you need to send one. IntakeQ: GET /questionnaires.

    Annotations the server declares

    • title: List questionnaire templates
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data6
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__intakeq__intakeq_send_questionnaire"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://intakeq.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://intakeq.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://intakeq.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://intakeq.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http intakeq https://intakeq.usefulapi.io/mcp
claude mcp add --transport http intakeq https://intakeq.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__intakeq__intakeq_list_clients",
      "mcp__intakeq__intakeq_get_client_diagnoses",
      "mcp__intakeq__intakeq_list_appointments",
      "mcp__intakeq__intakeq_get_appointment",
      "mcp__intakeq__intakeq_get_booking_settings",
      "mcp__intakeq__intakeq_list_intakes",
      "mcp__intakeq__intakeq_get_intake",
      "mcp__intakeq__intakeq_list_questionnaires",
      "mcp__intakeq__intakeq_list_practitioners",
      "mcp__intakeq__intakeq_list_notes",
      "mcp__intakeq__intakeq_get_note",
      "mcp__intakeq__intakeq_list_invoices",
      "mcp__intakeq__intakeq_get_invoice"
    ],
    "ask": [],
    "deny": [
      "mcp__intakeq__intakeq_save_client",
      "mcp__intakeq__intakeq_add_client_tag",
      "mcp__intakeq__intakeq_create_appointment",
      "mcp__intakeq__intakeq_update_appointment",
      "mcp__intakeq__intakeq_cancel_appointment",
      "mcp__intakeq__intakeq_send_questionnaire"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as intakeq. Review it before you use it.

Capability tags behind 8 rules
  • mcp__intakeq__intakeq_list_clients private-data, untrusted-input
  • mcp__intakeq__intakeq_get_client_diagnoses private-data
  • mcp__intakeq__intakeq_list_appointments private-data, untrusted-input
  • mcp__intakeq__intakeq_list_practitioners private-data, untrusted-input
  • mcp__intakeq__intakeq_list_notes private-data
  • mcp__intakeq__intakeq_get_note private-data
  • mcp__intakeq__intakeq_list_invoices untrusted-input
  • mcp__intakeq__intakeq_send_questionnaire outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/intakeq/verify?hash=96b5958e4998a241779863917ab4df84e0f240957b0e86dacb7c1d47f0ecea15" | jq -e '.changed == false'

Pinned hash 96b5958e4998, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/intakeq/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/intakeq
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/intakeq.svg)](https://radar.anlyon.com/servers/io.usefulapi/intakeq)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

IntakeQ MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the IntakeQ MCP by usefulapi safe?

No scan can promise that. What its definitions show: 19 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the IntakeQ MCP by usefulapi delete data?

Yes. 6 tools can delete, cancel or revoke something: intakeq_save_client, intakeq_add_client_tag, intakeq_create_appointment, intakeq_update_appointment, intakeq_cancel_appointment and intakeq_send_questionnaire.

Can the IntakeQ MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the IntakeQ MCP by usefulapi have?

19 tools: 6 destructive, 13 read. intakeq_save_client, intakeq_add_client_tag, intakeq_create_appointment, intakeq_update_appointment, intakeq_cancel_appointment, intakeq_send_questionnaire, intakeq_list_clients, intakeq_get_client_diagnoses and 11 more.

Does the IntakeQ MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the IntakeQ MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): intakeq_send_questionnaire.

Has the IntakeQ MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.