Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Redra 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.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search current class-action settlements and identify possible matches using structured filters.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http redra-mcp https://mcp.redra.ai/mcp
# 2 — ask your agent for something these tools do
# search_settlements, search_settlements_batch, get_settlement and 2 more
Redra costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SAAll 1 server
sacrosaunt1 server
1 category
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 redra-mcp https://mcp.redra.ai/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
5 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.
Search one settlement angle using logical AND keywords and structured status, type, state, proof, and deadline filters. Status defaults to open. Results include source metadata and quality flags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | no | Required logical-AND terms for specific companies, brands, products, employers, services, or incidents. Use separate queries for alternatives and settlement_type for taxonomy. | |
| state | no | Optional two-letter US postal abbreviation, such as CA. | |
| status | string | no | Public lifecycle filter: open or upcoming. Defaults to open. Upcoming records are not yet claimable and must be presented as a separate watchlist. |
| settlement_type | no | Exact settlement taxonomy filter. Prefer this over keywords for type concepts such as data breaches, privacy, refunds, financial fees, or consumer products. | |
| proof_required | no | Whether proof is required: yes, no, or unknown. | |
| deadline_after | no | Include deadlines on or after this ISO 8601 date. | |
| deadline_before | no | Include deadlines on or before this ISO 8601 date. | |
| limit | integer | no | Maximum records returned, from 1 to 50. |
Run up to 50 independent settlement searches and deduplicate records across queries. Results include matched_query_indices, and executed_query_count reports the number of searches performed. Use when several unrelated search angles should be evaluated together.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queries | array | yes | Independent settlement searches. Each query retains logical-AND keyword semantics; unrelated alternatives belong in separate query objects. |
| max_total_results | integer | no | Maximum unique settlement records returned across the whole batch after cross-query deduplication. This caps output, not the number of independent searches performed. |
Return the complete stored record and official source links for one settlement ID produced by a search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| settlement_id | string | yes | Exact settlement identifier returned by a search. |
Return complete stored records and official source links for up to 20 settlement IDs produced by search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| settlement_ids | array | yes | Settlement identifiers returned by search to retrieve together. |
Return source, license, freshness, counts, and hosted aggregate metrics.
No parameter schema on file.
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 Redra 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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 0.1.0.
0.1.0
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 Redra 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.