Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
nodrix 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.
95/100
trust score
28
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read live and historical IoT telemetry and actuate ESP32/Arduino hardware from a backend you host.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nodrix-mcp 'https://{host}/v1/mcp/oauth'
# 2 — ask your agent for something these tools do
# list_projects, list_variables, get_state and 25 more
The address is a placeholder from the publisher’s own docs: put the address of your own deployment in its place before you run this.
nodrix costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NOAll 1 server
nodrix1 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. The address on this listing is a placeholder from its publisher’s own docs, not a live endpoint: you run nodrix yourself and put the address of your own deployment in its place — this marketplace is not in the path.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. The address is a placeholder from the publisher’s own docs: put the address of your own deployment in its place before you run this. 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 nodrix-mcp 'https://{host}/v1/mcp/oauth'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at your own deployment of it: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it writes
One config entry pointing at the address of your own deployment — this marketplace is not in the path, and the server runs wherever you deploy it.
What you approve
28 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.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs at your own deployment of it — 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 nodrix 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: —
ATrust score 95 / 100
Release 1.0.1 · scanned 6 Oct 2026
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 score99
Client score95
Findings3 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest8227c42a0faa9b44ff6ade9177caa142421ac7414c58c5ccabd7b3909d956f18
Score vectorthreat 99 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (28 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| list_projects | no tags | |
| list_variables | no tags | |
| get_state | no tags | |
| get_series | no tags | |
| list_dashboards | no tags | |
| get_dashboard | no tags | |
| list_widget_types | no tags | |
| list_widgets | no tags | |
| list_block_types | no tags | |
| list_integration_kinds | no tags | |
| list_automations | no tags | |
| list_integrations | no tags | |
| create_project | no tags | |
| update_project | no tags | |
| create_variable | no tags | |
| update_variable | no tags | |
| set_variable | no tags | |
| create_dashboard | no tags | |
| update_dashboard | no tags | |
| add_widget | no tags | |
| update_widget | untrusted-input | untrusted-input: keyword "fetch" |
| create_automation | no tags | |
| update_automation | no tags | |
| run_automation | no tags | |
| emit_event | no tags | |
| create_integration | no tags | |
| update_integration | no tags | |
| test_integration | no tags |
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
Integrityfirst-seen
Surface digest8227c42a0faa9b44
Scanned2026-10-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
It answers at your own deployment of it, running whatever release you deployed there — so a release cannot be chosen from here. The history below is for reading; the current release on file is 1.0.1.
1.0.1
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 nodrix 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.