Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
ESQ Matching Engine 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.
What it does
Find and compare licensed US lawyers from official licensing records, with sources. No legal advice.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http esq-matching-engine-mcp https://match.esqcopilot.com/mcp/c/eyJrIjoiY29ubmVjdG9yIiwiaSI6ImNvbl9tY3BfcmVnaXN0cnlfZXNxIiwicCI6Im1jcC1yZWdpc3RyeSJ9.3b61cb285412dd02ba328c4c5ccd0b00
# 2 — ask your agent for something these tools do
# get_matching_requirements, find_attorneys, compare_attorneys and 7 more
ESQ Matching Engine costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 esq-matching-engine-mcp https://match.esqcopilot.com/mcp/c/eyJrIjoiY29ubmVjdG9yIiwiaSI6ImNvbl9tY3BfcmVnaXN0cnlfZXNxIiwicCI6Im1jcC1yZWdpc3RyeSJ9.3b61cb285412dd02ba328c4c5ccd0b00Reconnect, or start a new session, and the tools appear in the model’s tool list.
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.
10 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.
Use first when someone asks for a lawyer but the state or type of legal matter is unclear ("I need a lawyer", "help me with my landlord"). Returns the few questions still needed (state, matter type, location, timing, budget) and what was understood. Does not answer the legal question and stores nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | no | Short description of the legal need in the user's words. Used only to pick a practice area; not stored. |
| practice_area | string | no | Practice area, e.g. 'Landlord-Tenant Law', 'Family Law', 'Criminal Law' |
| subpractice_area | string | no | — |
| matter_type | string | no | — |
| category | string | no | — |
| procedural_stage | string | no | — |
| client_side | string | no | Which side the user is on. ESQ Matching Engine has no record of which side lawyers usually represent, so results carry a warning to ask. |
| service_needed | string | no | — |
| state | string | no | US state, two-letter code or name, e.g. CA or California |
| county | string | no | — |
| city | string | no | — |
| zip | string | no | 5-digit ZIP code, only if the user agreed to share it |
| court | string | no | — |
| remote_ok | boolean | no | User is willing to work with a lawyer remotely (phone or video) anywhere in the state |
| urgency | string | no | — |
| deadline_date | string | no | A deadline the USER reported (hearing, filing, response). ESQ Matching Engine does not verify or calculate deadlines. |
| deadline_type | string | no | — |
| consultation_by | string | no | Latest date the user wants a first consultation |
| representation_start_by | string | no | Date as YYYY-MM-DD |
| budget_max | number | no | Total budget the user mentioned, in US dollars |
Use when someone wants a lawyer for a U.S. legal matter, e.g. "find an affordable tenant lawyer in Santa Ana" or "I was fired after complaining, who can help in Los Angeles". Needs state and matter type (or a short description). Returns up to 5 licensed lawyers with reasons, a relevance score, a separate data_confidence level, license source and check date, whether they are known to take private c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | no | Short description of the legal need in the user's words. Used only to pick a practice area; not stored. |
| practice_area | string | no | Practice area, e.g. 'Landlord-Tenant Law', 'Family Law', 'Criminal Law' |
| subpractice_area | string | no | — |
| matter_type | string | no | — |
| category | string | no | — |
| procedural_stage | string | no | — |
| client_side | string | no | Which side the user is on. ESQ Matching Engine has no record of which side lawyers usually represent, so results carry a warning to ask. |
| service_needed | string | no | — |
| state | string | no | US state, two-letter code or name, e.g. CA or California |
| county | string | no | — |
| city | string | no | — |
| zip | string | no | 5-digit ZIP code, only if the user agreed to share it |
| court | string | no | — |
| remote_ok | boolean | no | User is willing to work with a lawyer remotely (phone or video) anywhere in the state |
| urgency | string | no | — |
| deadline_date | string | no | A deadline the USER reported (hearing, filing, response). ESQ Matching Engine does not verify or calculate deadlines. |
| deadline_type | string | no | — |
| consultation_by | string | no | Latest date the user wants a first consultation |
| representation_start_by | string | no | Date as YYYY-MM-DD |
| budget_max | number | no | Total budget the user mentioned, in US dollars |
Use when the user asks to compare lawyers from find_attorneys ("which of these is a better fit?"). Compares 2 to 5 lawyers on practice fit, location, years licensed, fees, availability, data confidence and gaps. Pass match_id to use the user's criteria. Says when prices or timing cannot be compared because the data is unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attorney_ids | array | yes | — |
| match_id | string | no | The match_id from find_attorneys, so comparisons use the same criteria |
| priorities | array | no | What matters most, in order. Shifts ranking weights. |
| criteria | array | no | — |
Use when the user asks what a lawyer or a type of matter will cost. Returns only published fees, confirmed quotes or sourced market figures, each labeled; says plainly when there is not enough data instead of guessing. Not a quote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| practice_area | string | no | — |
| description | string | no | Short description of the legal need in the user's words. Used only to pick a practice area; not stored. |
| state | string | no | US state, two-letter code or name, e.g. CA or California |
| scope | string | no | — |
| billing_preference | string | no | — |
| budget_max | number | no | Total budget the user mentioned, in US dollars |
| attorney_id | string | no | — |
Use when the user asks whether a lawyer takes new clients or can meet soon. Returns only what lawyers reported or confirmed, with last-checked time and certainty (reported, tentative, confirmed); unknown when nothing was reported. There is no live calendar access.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attorney_ids | array | yes | — |
| wanted_by | string | no | Latest acceptable consultation date |
| time_zone | string | no | — |
| appointment_type | string | no | — |
Use when the user wants details on one lawyer from a match. Returns license status with its official source and check date, private-client intake evidence, practice areas, service area, fees, availability, languages, data freshness, the directory profile link and a suggested citation. Also returns the exact consent text to show before an introduction.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attorney_id | string | yes | — |
Use only when the user asks to be introduced to ONE specific lawyer AND has seen that lawyer's name, the exact details to be shared and the consent text from get_attorney_profile, then said yes. Never call it on your own initiative or for several lawyers at once. Stores only the authorized fields; retries with the same idempotency_key do not duplicate. IMPORTANT: sending to lawyers is currently sw
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attorney_id | string | yes | — |
| match_id | string | no | — |
| practice_area | string | no | — |
| state | string | yes | US state, two-letter code or name, e.g. CA or California |
| contact | object | yes | — |
| matter_summary | string | yes | Summary the USER read and approved for sharing with this lawyer |
| preferred_contact_method | string | yes | — |
| preferred_timeframe | string | no | — |
| consent | object | yes | — |
| idempotency_key | string | no | Same key on retries prevents a duplicate introduction |
| attribution_token | string | no | Signed campaign/partner token issued by ESQ Matching Engine, if the user arrived through a partner link |
Use when the user asks what happened with an introduction. Returns lifecycle_state (recorded, queued, sent, delivered, responded, consultation_requested, consultation_confirmed, cancelled, completed, failed), whether it reached the lawyer, the lawyer's response and consultation state. Needs the private status_token. A consultation counts only when confirmed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| referral_id | string | yes | — |
| status_token | string | no | The status_token returned when the introduction was created |
Save or change matching criteria (location, budget, timing, practice area, language, priorities) for this conversation. No personal contact details. Deleted automatically after 24 hours.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| preference_set_id | string | no | Omit to create a new set |
| criteria | object | yes | Fields to set or change. Do not include names, emails or phone numbers. |
| clear_fields | array | no | — |
Optional 1-5 ratings on match relevance, lawyer responsiveness, pricing and availability accuracy, satisfaction, and whether the lawyer was hired. No case details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| match_id | string | no | — |
| referral_id | string | no | — |
| status_token | string | no | — |
| relevance | integer | no | — |
| responsiveness | integer | no | — |
| pricing_accuracy | integer | no | — |
| availability_accuracy | integer | no | — |
| satisfaction_match | integer | no | — |
| satisfaction_process | integer | no | — |
| satisfaction_attorney | integer | no | — |
| retained | string | no | — |
| comment | string | no | Optional. Do not include case details. |
- 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 ESQ Matching Engine or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| get_matching_requirements | no tags | |
| find_attorneys | no tags | |
| compare_attorneys | no tags | |
| estimate_legal_cost | no tags | |
| check_attorney_availability | no tags | |
| get_attorney_profile | no tags | |
| request_attorney_introduction | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_referral_status | no tags | |
| update_matching_preferences | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| submit_matching_feedback | state-write | state-write: declares readOnlyHint: false |
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
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.4.0.
No release note was published with this version.
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.
Any signed-in account that does not publish ESQ Matching Engine can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.