Hubitat MCP Server (rfhayn/hubitat-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 14 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
50/100

Hubitat MCP Server

Enables Claude to control Hubitat smart home hub devices, modes, HSM, and variables via MCP tools, with remote access via ngrok and device aliasing.

→ rfhayn/hubitat-mcp-server· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

rfhayn

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: HUBITAT_ACCESS_TOKEN, MCP_AUTH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes14 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_devices

List all authorized Hubitat devices with their names and types

get_device

Get detailed info for a device including current attributes, capabilities, and available commands

send_command

Send a command to a device (e.g., on, off, setLevel, lock, unlock, setColor)

get_device_events

Get recent event history for a device (state changes, commands)

get_devices_by_capability
get_devices_by_room

Get all devices in a specific room with their key attributes

send_commands_batch

Send commands to multiple devices in parallel. One failure does not block others.

get_hsm_status

Get the current Hubitat Safety Monitor (HSM) status (armed/disarmed state)

set_hsm
get_modes

List all available hub modes and which one is currently active

get_current_mode

Get the currently active hub mode

set_mode

Change the hub mode (e.g., Home, Away, Night)

get_variable

Get the current value of a hub variable

set_variable

Set the value of a hub variable

// known CVEs in dependencies1 critical3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.0.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.12.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretHUBITAT_ACCESS_TOKENxxx # Maker API access token
configHUBITAT_APP_ID42 # Maker API app ID
configHUBITAT_HOST192.168.1.100 # Your hub's IP address
🔐 secretMCP_AUTH_TOKENxxx # Bearer token (auto-generated by setup)
configMCP_HTTP_PORT3000 # Port for HTTP transport
configMCP_TRANSPORThttp # "stdio" or "http"
configNGROK_AUTHTOKENxxx # From ngrok dashboard
configNGROK_DOMAINyou.ngrok-free.app # Free static domain
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

14/14 tools missing one or more hints — list_devices (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_device (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); send_command (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

9/14 tool handlers declare input schemas (64%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/14 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/14 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 9 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/rfhayn/hubitat-mcp-server?variant=verified)](https://m8ven.ai/mcp/rfhayn/hubitat-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: be592da663078e508311f70291636127931ab116
code hash: 7dbf4c4a2bb67fd00c97fb8785cd591391ac047179e1ef6b6555d00f15efac5d
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client