Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Lawcus 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.
93/100
tool-list score
27
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read Lawcus contacts, matters, leads, time and billing reports; create contacts and tasks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lawcus-mcp-by-usefulapi https://lawcus.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# lawcus_get_me, lawcus_get_firm, lawcus_list_team_members and 24 more
Lawcus 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 578 servers
usefulapi578 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 lawcus-mcp-by-usefulapi https://lawcus.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
27 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.
Lawcus: the user the API token belongs to (id, uuid, name, timezone, role such as OWNER/ADMIN/MEMBER).
No parameter schema on file.
Lawcus: the firm (team) details: name, address, currency, locale and phone numbers.
No parameter schema on file.
Lawcus: the people on the firm's team with id, uuid, name, role and hourly rate. Ids are used in matter, task and report filters.
No parameter schema on file.
Lawcus: global search across contacts, matters and leads for a keyword.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| terms | string | yes | Keyword to search for. |
Lawcus: list contacts (people and companies; clients are contacts), filterable by name, email, type or update date. Paged with skip/take.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name_contains | string | no | Substring of the contact's full name. |
| email_contains | string | no | — |
| type | string | no | — |
| updated_after | string | no | A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss). |
| filters | array | no | Advanced: extra Lawcus v2 filter objects {field, operator, value}, ANDed with the other filters. Dates are 'yyyy-mm-dd hh:mm:ss' UTC. |
| sort_by | string | no | — |
| sort_order | string | no | — |
| skip | integer | no | Records to skip (default 0). Pass the previous reply's next_skip. |
| take | integer | no | Records per page (default 25, max 100). |
Lawcus: one contact by UUID, with addresses, phones, emails and custom fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_uuid | string | yes | — |
WRITE: create a new contact in Lawcus (a person or a company). It does not send anything to the contact. Person needs first_name and last_name; Company needs name. Check lawcus_list_contacts first to avoid duplicates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| first_name | string | no | Required for a Person. |
| last_name | string | no | Required for a Person. |
| name | string | no | Required for a Company. |
| string | no | — | |
| phone | string | no | — |
| title | string | no | Business title. |
| website | string | no | — |
| note | string | no | — |
| street | string | no | — |
| city | string | no | — |
| state | string | no | — |
| zip | string | no | — |
| country | string | no | — |
Lawcus: list matters (cases) with status, client, billing type, trust and retainer balances. Filter by status, name, number, client or dates. Paged with skip/take; the reply also carries opened/closed counts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Matter status, e.g. "OPEN" or "CLOSED". |
| name_contains | string | no | — |
| number | string | no | Matter number (exact). |
| client_id | integer | no | Numeric id of the client contact. |
| responsible_attorney_id | integer | no | Numeric user id. |
| opened_after | string | no | A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss). |
| updated_after | string | no | A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss). |
| filters | array | no | Advanced: extra Lawcus v2 filter objects {field, operator, value}, ANDed with the other filters. Dates are 'yyyy-mm-dd hh:mm:ss' UTC. |
| sort_by | string | no | — |
| sort_order | string | no | — |
| skip | integer | no | Records to skip (default 0). Pass the previous reply's next_skip. |
| take | integer | no | Records per page (default 25, max 100). |
Lawcus: one matter by UUID with its client, workflow stage, billing settings, balances and custom fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| matter_uuid | string | yes | — |
Lawcus: list leads (prospective matters) with client contact details and pipeline stage. Paged with skip/take.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name_contains | string | no | — |
| stage_id | integer | no | Pipeline stage id (see lawcus_list_workflow_stages). |
| lead_source_id | integer | no | Lead source id (see lawcus_list_lead_sources). |
| created_after | string | no | Only leads created after this UTC time. |
| filters | array | no | Advanced: extra Lawcus v2 filter objects {field, operator, value}, ANDed with the other filters. Dates are 'yyyy-mm-dd hh:mm:ss' UTC. |
| sort_by | string | no | — |
| sort_order | string | no | — |
| skip | integer | no | Records to skip (default 0). Pass the previous reply's next_skip. |
| take | integer | no | Records per page (default 25, max 100). |
Lawcus: one lead by UUID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_uuid | string | yes | — |
Lawcus: the firm's lead sources (Website, Referral, Google, ...). Ids go into lead and contact filters.
No parameter schema on file.
Lawcus: the workflows (matter and lead pipelines) with their ids.
No parameter schema on file.
Lawcus: the stages of one workflow (pipeline).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflow_id | string | yes | Workflow id from lawcus_list_workflows. |
Lawcus: list tasks, optionally by completion, assignee, matter or tag. The API returns the whole list; the reply is cut to limit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| completed | boolean | no | true = completed tasks, false = open tasks. |
| delegated | boolean | no | true = tasks delegated to others. |
| user_id | string | no | UUID of the assignee (the uuid from lawcus_list_team_members). |
| matter_id | integer | no | Numeric matter id. |
| tags | string | no | Tag name, e.g. "San Diego Branch". |
| limit | integer | no | Return at most this many records (default 100, max 500). The reply says when the list was cut. |
WRITE: create a task in Lawcus, optionally on a matter and assigned to team members. Lawcus may email or SMS the assignees if reminders are set; no reminders are set by this tool.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| description | string | no | — |
| due_date | string | no | A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss). |
| matter_id | integer | no | Numeric matter id (the id of a matter). |
| assignee_uuids | array | no | UUIDs of the users to assign (from lawcus_list_team_members). |
Lawcus: time entries (hours worked, rate, total, matter, invoiced or not). The API returns all entries; filter here by matter and date range, reply cut to limit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| matter_id | integer | no | — |
| user_id | integer | no | — |
| date_from | string | no | A date, yyyy-mm-dd. |
| date_to | string | no | A date, yyyy-mm-dd. |
| limit | integer | no | Return at most this many records (default 100, max 500). The reply says when the list was cut. |
Lawcus: expenses logged against matters. The API returns all expenses; filter here by matter and date range, reply cut to limit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| matter_id | integer | no | — |
| date_from | string | no | A date, yyyy-mm-dd. |
| date_to | string | no | A date, yyyy-mm-dd. |
| limit | integer | no | Return at most this many records (default 100, max 500). The reply says when the list was cut. |
Lawcus: billable activity (time entries, expenses and flat fees) with payment details, filterable by date range, user, practice area, matter, client and invoiced state. Also returns time totals for today/week/month/year.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| kind | string | no | Only this kind of item (default: all three). |
| user_id | integer | no | — |
| practice_id | integer | no | — |
| matter_id | integer | no | — |
| client_id | integer | no | — |
| is_invoiced | boolean | no | — |
| limit | integer | no | Return at most this many records (default 100, max 500). The reply says when the list was cut. |
Lawcus: logged client interactions (emails, calls, secure messages) with subject, matter and contact. Paged with skip/paginate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| types | array | no | Interaction types (default: all). |
| direction | string | no | — |
| skip | integer | no | — |
| paginate | integer | no | Page size (default 20, max 100). |
Lawcus report (needs the Admin role): unpaid invoices by age (who owes the firm what).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| user_id | integer | no | Numeric user id. |
| practice_id | integer | no | Numeric practice area id. |
| client_id | integer | no | Numeric client contact id. |
| matter_id | integer | no | Numeric matter id. |
| group_by | string | no | Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries). |
Lawcus report (needs the Admin role): balance summary of all matters, optionally trust balances only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| user_id | integer | no | Numeric user id. |
| practice_id | integer | no | Numeric practice area id. |
| client_id | integer | no | Numeric client contact id. |
| group_by | string | no | Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries). |
| trust | boolean | no | true = trust balances. |
Lawcus report (needs the Admin role): revenue by attorney for a period.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| user_id | integer | no | Numeric user id. |
| client_id | integer | no | Numeric client contact id. |
| matter_id | integer | no | Numeric matter id. |
Lawcus report (needs the Admin role): time entries summarized per user for a period.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| user_id | integer | no | Numeric user id. |
| matter_id | integer | no | Numeric matter id. |
| group_by | string | no | Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries). |
Lawcus report (needs the Admin role): payments the firm collected in a period.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| user_id | integer | no | Numeric user id. |
| practice_id | integer | no | Numeric practice area id. |
| client_id | integer | no | Numeric client contact id. |
| matter_id | integer | no | Numeric matter id. |
Lawcus report (needs the Admin role): summary of issued invoices for a period.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| user_id | integer | no | Numeric user id. |
| practice_id | integer | no | Numeric practice area id. |
| client_id | integer | no | Numeric client contact id. |
| group_by | string | no | Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries). |
Lawcus report (needs the Admin role): client trust (IOLTA) balances; zero balances hidden unless display_zero is true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss. |
| end | string | no | Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss. |
| practice_id | integer | no | Numeric practice area id. |
| client_id | integer | no | Numeric client contact id. |
| display_zero | boolean | no | — |
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 Lawcus 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 93 / 100
Release 1.15.3 · scanned 6 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 score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest802d8b041ad06fadcffe378b0ec233fb70ef69a0b6cdfea31f7f2ca205fa8de3
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| lawcus_get_me | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_get_firm | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_team_members | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_contacts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_get_contact | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_create_contact | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| lawcus_list_matters | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_get_matter | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_leads | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_get_lead | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_lead_sources | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_workflows | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_workflow_stages | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_tasks | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_create_task | external-sink | external-sink: keyword "sms", declares readOnlyHint: false, openWorldHint: true |
| lawcus_list_time_entries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_expenses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_billing_items | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_list_interactions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_report_accounts_receivable | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_report_matter_balance | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_report_revenue | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_report_time_entries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_report_payments_collected | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_report_invoice_history | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lawcus_report_client_trust | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest802d8b041ad06fad
Scanned2026-11-06
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.15.3.
1.15.3
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 Lawcus 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.