Lawcus MCP by usefulapi
REMOTE · LAWCUS.USEFULAPI.IO
Read Lawcus contacts, matters, leads, time and billing reports; create contacts and tasks.
Available components
Last scanned (4 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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 Security78
- 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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% 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
- We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 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
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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 Oct 26 60
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 25 Oct 2026 · Probed https://lawcus.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 lawcus.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://lawcus.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://lawcus.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://lawcus.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://lawcus.usefulapi.io/mcp |
| Authorisation server | https://lawcus.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lawcus.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/lawcus/ |
| http (plaintext) | http://lawcus.usefulapi.io/mcp | Inconclusive | 302 | http://lawcus.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 →
lawcus_create_contact ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| country | string | – | – |
| 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 | yes | – |
| website | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
lawcus_create_task ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
lawcus_get_contact ~36
Lawcus: one contact by UUID, with addresses, phones, emails and custom fields.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_uuid | string | yes | – |
No output schema declared.
No examples provided.
lawcus_get_firm ~32
Lawcus: the firm (team) details: name, address, currency, locale and phone numbers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lawcus_get_lead ~27
Lawcus: one lead by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_uuid | string | yes | – |
No output schema declared.
No examples provided.
lawcus_get_matter ~41
Lawcus: one matter by UUID with its client, workflow stage, billing settings, balances and custom fields.
| Name | Type | Req | Description |
|---|---|---|---|
| matter_uuid | string | yes | – |
No output schema declared.
No examples provided.
lawcus_get_me ~38
Lawcus: the user the API token belongs to (id, uuid, name, timezone, role such as OWNER/ADMIN/MEMBER).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lawcus_list_billing_items ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
lawcus_list_contacts ~196
Lawcus: list contacts (people and companies; clients are contacts), filterable by name, email, type or update date. Paged with skip/take.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
lawcus_list_expenses ~105
Lawcus: expenses logged against matters. The API returns all expenses; filter here by matter and date range, reply cut to `limit`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
lawcus_list_interactions ~84
Lawcus: logged client interactions (emails, calls, secure messages) with subject, matter and contact. Paged with skip/paginate.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| paginate | integer | – | Page size (default 20, max 100). |
| skip | integer | – | – |
| types | array | – | Interaction types (default: all). |
No output schema declared.
No examples provided.
lawcus_list_lead_sources ~37
Lawcus: the firm's lead sources (Website, Referral, Google, ...). Ids go into lead and contact filters.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lawcus_list_leads ~196
Lawcus: list leads (prospective matters) with client contact details and pipeline stage. Paged with skip/take.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
lawcus_list_matters ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
lawcus_list_tasks ~153
Lawcus: list tasks, optionally by completion, assignee, matter or tag. The API returns the whole list; the reply is cut to `limit`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
lawcus_list_team_members ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lawcus_list_time_entries ~125
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
lawcus_list_workflow_stages ~40
Lawcus: the stages of one workflow (pipeline).
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | Workflow id from lawcus_list_workflows. |
No output schema declared.
No examples provided.
lawcus_list_workflows ~26
Lawcus: the workflows (matter and lead pipelines) with their ids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lawcus_report_accounts_receivable ~171
Lawcus report (needs the Admin role): unpaid invoices by age (who owes the firm what).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lawcus_report_client_trust ~133
Lawcus report (needs the Admin role): client trust (IOLTA) balances; zero balances hidden unless display_zero is true.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lawcus_report_invoice_history ~156
Lawcus report (needs the Admin role): summary of issued invoices for a period.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lawcus_report_matter_balance ~171
Lawcus report (needs the Admin role): balance summary of all matters, optionally trust balances only.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lawcus_report_payments_collected ~138
Lawcus report (needs the Admin role): payments the firm collected in a period.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lawcus_report_revenue ~123
Lawcus report (needs the Admin role): revenue by attorney for a period.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lawcus_report_time_entries ~144
Lawcus report (needs the Admin role): time entries summarized per user for a period.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lawcus_search ~35
Lawcus: global search across contacts, matters and leads for a keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| terms | string | yes | Keyword to search for. |
No output schema declared.
No examples provided.
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.
remote · lawcus.usefulapi.io
claude mcp add --transport http io-usefulapi-lawcus 'https://lawcus.usefulapi.io/mcp'
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.