# Lawcus MCP by usefulapi (remote · lawcus.usefulapi.io)

Read Lawcus contacts, matters, leads, time and billing reports; create contacts and tasks.

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

## Components

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

## Channel facts

- Endpoint: `https://lawcus.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.3`

## 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-25.

- **Endpoint Security**: 78/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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3304 tokens (~122/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% 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.
  - We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 28 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 Lawcus MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-lawcus": {
      "type": "http",
      "url": "https://lawcus.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-25 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.1.3

### 2026-10-24 (score 60)

First indexed and scored.

## MCP tools (27)

### `lawcus_get_me` (~38 tokens)

Lawcus: the user the API token belongs to (id, uuid, name, timezone, role such as OWNER/ADMIN/MEMBER).

### `lawcus_get_firm` (~32 tokens)

Lawcus: the firm (team) details: name, address, currency, locale and phone numbers.

### `lawcus_list_team_members` (~44 tokens)

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.

### `lawcus_search` (~35 tokens)

Lawcus: global search across contacts, matters and leads for a keyword.

Input parameters:

- `terms` (string, required): Keyword to search for.

### `lawcus_list_contacts` (~196 tokens)

Lawcus: list contacts (people and companies; clients are contacts), filterable by name, email, type or update date. Paged with skip/take.

Input parameters:

- `email_contains` (string)
- `filters` (array): Advanced: extra Lawcus v2 filter objects {field, operator, value}, ANDed with the other filters. Dates are 'yyyy-mm-dd hh:mm:ss' UTC.
- `name_contains` (string): Substring of the contact's full name.
- `skip` (integer): Records to skip (default 0). Pass the previous reply's next_skip.
- `sort_by` (string)
- `sort_order` (string)
- `take` (integer): Records per page (default 25, max 100).
- `type` (string)
- `updated_after` (string): A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss).

### `lawcus_get_contact` (~36 tokens)

Lawcus: one contact by UUID, with addresses, phones, emails and custom fields.

Input parameters:

- `contact_uuid` (string, required)

### `lawcus_create_contact` (~171 tokens)

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.

Input parameters:

- `city` (string)
- `country` (string)
- `email` (string)
- `first_name` (string): Required for a Person.
- `last_name` (string): Required for a Person.
- `name` (string): Required for a Company.
- `note` (string)
- `phone` (string)
- `state` (string)
- `street` (string)
- `title` (string): Business title.
- `type` (string, required)
- `website` (string)
- `zip` (string)

### `lawcus_list_matters` (~274 tokens)

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.

Input parameters:

- `client_id` (integer): Numeric id of the client contact.
- `filters` (array): Advanced: extra Lawcus v2 filter objects {field, operator, value}, ANDed with the other filters. Dates are 'yyyy-mm-dd hh:mm:ss' UTC.
- `name_contains` (string)
- `number` (string): Matter number (exact).
- `opened_after` (string): A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss).
- `responsible_attorney_id` (integer): Numeric user id.
- `skip` (integer): Records to skip (default 0). Pass the previous reply's next_skip.
- `sort_by` (string)
- `sort_order` (string)
- `status` (string): Matter status, e.g. "OPEN" or "CLOSED".
- `take` (integer): Records per page (default 25, max 100).
- `updated_after` (string): A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss).

### `lawcus_get_matter` (~41 tokens)

Lawcus: one matter by UUID with its client, workflow stage, billing settings, balances and custom fields.

Input parameters:

- `matter_uuid` (string, required)

### `lawcus_list_leads` (~196 tokens)

Lawcus: list leads (prospective matters) with client contact details and pipeline stage. Paged with skip/take.

Input parameters:

- `created_after` (string): Only leads created after this UTC time.
- `filters` (array): Advanced: extra Lawcus v2 filter objects {field, operator, value}, ANDed with the other filters. Dates are 'yyyy-mm-dd hh:mm:ss' UTC.
- `lead_source_id` (integer): Lead source id (see lawcus_list_lead_sources).
- `name_contains` (string)
- `skip` (integer): Records to skip (default 0). Pass the previous reply's next_skip.
- `sort_by` (string)
- `sort_order` (string)
- `stage_id` (integer): Pipeline stage id (see lawcus_list_workflow_stages).
- `take` (integer): Records per page (default 25, max 100).

### `lawcus_get_lead` (~27 tokens)

Lawcus: one lead by UUID.

Input parameters:

- `lead_uuid` (string, required)

### `lawcus_list_lead_sources` (~37 tokens)

Lawcus: the firm's lead sources (Website, Referral, Google, ...). Ids go into lead and contact filters.

### `lawcus_list_workflows` (~26 tokens)

Lawcus: the workflows (matter and lead pipelines) with their ids.

### `lawcus_list_workflow_stages` (~40 tokens)

Lawcus: the stages of one workflow (pipeline).

Input parameters:

- `workflow_id` (string, required): Workflow id from lawcus_list_workflows.

### `lawcus_list_tasks` (~153 tokens)

Lawcus: list tasks, optionally by completion, assignee, matter or tag. The API returns the whole list; the reply is cut to `limit`.

Input parameters:

- `completed` (boolean): true = completed tasks, false = open tasks.
- `delegated` (boolean): true = tasks delegated to others.
- `limit` (integer): Return at most this many records (default 100, max 500). The reply says when the list was cut.
- `matter_id` (integer): Numeric matter id.
- `tags` (string): Tag name, e.g. "San Diego Branch".
- `user_id` (string): UUID of the assignee (the `uuid` from lawcus_list_team_members).

### `lawcus_create_task` (~135 tokens)

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.

Input parameters:

- `assignee_uuids` (array): UUIDs of the users to assign (from lawcus_list_team_members).
- `description` (string)
- `due_date` (string): A UTC date (yyyy-mm-dd) or timestamp (yyyy-mm-dd hh:mm:ss).
- `matter_id` (integer): Numeric matter id (the `id` of a matter).
- `name` (string, required)

### `lawcus_list_time_entries` (~125 tokens)

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`.

Input parameters:

- `date_from` (string): A date, yyyy-mm-dd.
- `date_to` (string): A date, yyyy-mm-dd.
- `limit` (integer): Return at most this many records (default 100, max 500). The reply says when the list was cut.
- `matter_id` (integer)
- `user_id` (integer)

### `lawcus_list_expenses` (~105 tokens)

Lawcus: expenses logged against matters. The API returns all expenses; filter here by matter and date range, reply cut to `limit`.

Input parameters:

- `date_from` (string): A date, yyyy-mm-dd.
- `date_to` (string): A date, yyyy-mm-dd.
- `limit` (integer): Return at most this many records (default 100, max 500). The reply says when the list was cut.
- `matter_id` (integer)

### `lawcus_list_billing_items` (~211 tokens)

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.

Input parameters:

- `client_id` (integer)
- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `is_invoiced` (boolean)
- `kind` (string): Only this kind of item (default: all three).
- `limit` (integer): Return at most this many records (default 100, max 500). The reply says when the list was cut.
- `matter_id` (integer)
- `practice_id` (integer)
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.
- `user_id` (integer)

### `lawcus_list_interactions` (~84 tokens)

Lawcus: logged client interactions (emails, calls, secure messages) with subject, matter and contact. Paged with skip/paginate.

Input parameters:

- `direction` (string)
- `paginate` (integer): Page size (default 20, max 100).
- `skip` (integer)
- `types` (array): Interaction types (default: all).

### `lawcus_report_accounts_receivable` (~171 tokens)

Lawcus report (needs the Admin role): unpaid invoices by age (who owes the firm what).

Input parameters:

- `client_id` (integer): Numeric client contact id.
- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `group_by` (string): Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries).
- `matter_id` (integer): Numeric matter id.
- `practice_id` (integer): Numeric practice area id.
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.
- `user_id` (integer): Numeric user id.

### `lawcus_report_matter_balance` (~171 tokens)

Lawcus report (needs the Admin role): balance summary of all matters, optionally trust balances only.

Input parameters:

- `client_id` (integer): Numeric client contact id.
- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `group_by` (string): Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries).
- `practice_id` (integer): Numeric practice area id.
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.
- `trust` (boolean): true = trust balances.
- `user_id` (integer): Numeric user id.

### `lawcus_report_revenue` (~123 tokens)

Lawcus report (needs the Admin role): revenue by attorney for a period.

Input parameters:

- `client_id` (integer): Numeric client contact id.
- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `matter_id` (integer): Numeric matter id.
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.
- `user_id` (integer): Numeric user id.

### `lawcus_report_time_entries` (~144 tokens)

Lawcus report (needs the Admin role): time entries summarized per user for a period.

Input parameters:

- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `group_by` (string): Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries).
- `matter_id` (integer): Numeric matter id.
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.
- `user_id` (integer): Numeric user id.

### `lawcus_report_payments_collected` (~138 tokens)

Lawcus report (needs the Admin role): payments the firm collected in a period.

Input parameters:

- `client_id` (integer): Numeric client contact id.
- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `matter_id` (integer): Numeric matter id.
- `practice_id` (integer): Numeric practice area id.
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.
- `user_id` (integer): Numeric user id.

### `lawcus_report_invoice_history` (~156 tokens)

Lawcus report (needs the Admin role): summary of issued invoices for a period.

Input parameters:

- `client_id` (integer): Numeric client contact id.
- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `group_by` (string): Grouping, e.g. client (accounts receivable, invoice history, matter balance) or teammate (time entries).
- `practice_id` (integer): Numeric practice area id.
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.
- `user_id` (integer): Numeric user id.

### `lawcus_report_client_trust` (~133 tokens)

Lawcus report (needs the Admin role): client trust (IOLTA) balances; zero balances hidden unless display_zero is true.

Input parameters:

- `client_id` (integer): Numeric client contact id.
- `display_zero` (boolean)
- `end` (string): Period end, UTC: yyyy-mm-dd (through 23:59:59) or yyyy-mm-dd hh:mm:ss.
- `practice_id` (integer): Numeric practice area id.
- `start` (string): Period start, UTC: yyyy-mm-dd (from 00:00:00) or yyyy-mm-dd hh:mm:ss.

## Diagnostics

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

## Score history

- 2026-10-25: 61
- 2026-10-24: 60

## Common questions

### What is the Lawcus MCP by usefulapi server?

Lawcus MCP by usefulapi is listed in the public MCP registry as io.usefulapi/lawcus. Read Lawcus contacts, matters, leads, time and billing reports; create contacts and tasks. This page covers its hosted endpoint (https://lawcus.usefulapi.io/mcp).

### Is the Lawcus MCP by usefulapi server safe to use?

Lawcus MCP by usefulapi scores 61 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 Lawcus MCP by usefulapi server expose?

Lawcus MCP by usefulapi exposes 27 tools: lawcus_get_me, lawcus_get_firm, lawcus_list_team_members, lawcus_search, lawcus_list_contacts, and 22 more. Their descriptions and schemas cost roughly 3,042 tokens of context every time the server is loaded.

### Does the Lawcus MCP by usefulapi server require authentication?

Yes. Lawcus MCP by usefulapi 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 Lawcus MCP by usefulapi server still maintained?

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