Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
CareLineLive MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read carers, teams, leave and visit rounds; update carer payroll codes in CareLineLive.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http carelinelive-mcp-by-usefulapi https://carelinelive.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# carelinelive_list_carers, carelinelive_get_carer, carelinelive_list_clients and 11 more
CareLineLive MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 598 servers
usefulapi598 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http carelinelive-mcp-by-usefulapi https://carelinelive.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List carers (care workers) in the CareLineLive environment, with their contract, team and employment fields. Filters are partial matches; not_on_leave excludes carers on leave in a period. CareLineLive API: GET /api/v2/carers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first_name | string | no | Partial match on first name. |
| last_name | string | no | Partial match on last name. |
| string | no | Partial match on email. | |
| payroll_number | string | no | Partial match on payroll number. |
| not_on_leave | string | no | Exclude carers with leave overlapping this period: 'from,to' as YYYY-MM-DD,YYYY-MM-DD (to must be after from). |
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
Show one carer by id, with optional related resources. CareLineLive API: GET /api/v2/carers/{carer}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| carer_id | string | yes | The id of the record. |
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
List clients (people receiving care) with their details and status. CareLineLive API: GET /api/v2/clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
Show one client by id, with optional related resources. CareLineLive API: GET /api/v2/clients/{client}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | string | yes | The id of the record. |
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
List office users (accounts that sign in to CareLineLive). CareLineLive API: GET /api/v2/users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_by | string | no | Comma-separated fields to sort by. |
| direction | string | no | Comma-separated sort directions, matching order_by (asc or desc). |
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
Show one office user by id. CareLineLive API: GET /api/v2/users/{user}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | yes | The id of the record. |
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
List the teams (branches or groups of carers and clients) in the environment. CareLineLive API: GET /api/v2/teams.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
List visit rounds (planned visit runs for carers). CareLineLive API: GET /api/v2/visit-rounds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
List carer leave records (holiday and other absences). CareLineLive API: GET /api/v2/leaves.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
List recorded incidents (care events that need follow-up). CareLineLive API: GET /api/v2/incidents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
List the public holidays set up for the environment. CareLineLive API: GET /api/v2/public-holidays.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
List the work patterns (standard weekly hours) used to plan carer contracts. CareLineLive API: GET /api/v2/work-patterns.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
List the permissions in the environment, so you can see what the access token can read. CareLineLive API: GET /api/v2/permissions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include | string | no | Comma-separated related resources to include in the reply, for example 'teams'. |
| page | integer | no | Page number (default 1). The reply's links.next and meta.pagination show whether more pages exist. |
| limit | integer | no | Records per page (default 25). |
Change a carer's payroll number, payroll department code or cost centre code. Only the fields you send change; sending the same values again has no further effect. Other carer fields are not changed by this tool. CareLineLive API: PATCH /api/v2/carers/{carer}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| carer_id | string | yes | The id of the record. |
| payroll_number | no | New payroll number, or null to clear it. | |
| payroll_department_code | no | New payroll department code, or null to clear it. | |
| cost_centre_code | no | New cost centre code, or null to clear it. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CareLineLive MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.2 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest84c0563db9cada2302f69d3c9de780b420df32ac8d0974dd7474476a3a1c4bd6
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| carelinelive_list_carers | no tags | |
| carelinelive_get_carer | no tags | |
| carelinelive_list_clients | no tags | |
| carelinelive_get_client | no tags | |
| carelinelive_list_users | no tags | |
| carelinelive_get_user | no tags | |
| carelinelive_list_teams | no tags | |
| carelinelive_list_visit_rounds | no tags | |
| carelinelive_list_leaves | no tags | |
| carelinelive_list_incidents | no tags | |
| carelinelive_list_public_holidays | no tags | |
| carelinelive_list_work_patterns | no tags | |
| carelinelive_list_permissions | no tags | |
| carelinelive_update_carer | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest84c0563db9cada23
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.2.
1.1.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish CareLineLive MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.