aha-mcp (sergiolopezgsiot/aha-mcp) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 18 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
58/100

aha-mcp

Enables natural language interaction with Home Assistant for managing entities, automations, services, and dashboards via the Model Context Protocol.

→ sergiolopezgsiot/aha-mcp· 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

sergiolopezgsiot

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, 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: HASS_ACCESS_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes18 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.

delete-automation

Delete an automation by id

update-automation-by-entity-id

Update an automation using its entity_id (e.g. automation.my_automation).

update-rest-automation-by-rest-id

Update an automation using its rest_id (REST API id, not entity_id).

delete-rest-automation-by-rest-id

Delete an automation using its rest_id (REST API id, not entity_id).

create-rest-automation

Create a new automation via the Home Assistant REST API. Returns the new rest_id.

validate-config

Validate triggers, conditions and actions configurations as if part of an automation. Any changes to automation should be checked with this tool

call-service

Call a Home Assistant service

update-lovelace-config

Update Lovelace dashboard config by url_path.

create-lovelace-dashboard

Create a new Lovelace dashboard.

delete-lovelace-dashboard

Delete a Lovelace dashboard by dashboard_id.

update-device-registry

Update the device registry for a specific device_id

create-config-entry-flow

Create a new config entry in the Home Assistant entity registry for a new config entry (new templated helpers for ex)

continue-config-entry-flow

Continue an existing config entry flow with a next step Id

finish-config-entry-flow

Finish an existing config entry flow

create-config-entry-options-flow

Create a new config entry options flow for a specific config entry (already existing config entry, templated helpers for ex)

update-config-entry-options-flow

Update an existing config entry options flow

upsertScriptRest-rest-script-by-alias

Create or Update the details of a specific script by its alias

delete-rest-script-by-alias

Delete a specific script by its alias

// known CVEs in dependencies1 critical4 high

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

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

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

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

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

high@modelcontextprotocol/inspector@0.16.5GHSA-g9hg-qhmf-q45m

MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server

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.
🔐 secretHASS_ACCESS_TOKEN"": "<your_token_here>"
configHASS_URL"": "https://your-home-assistant.local:8123",
configLIMIT_RESOURCESSet to a number to limit the number of resources returned by the server. Default: unlimited.
configRESOURCES_TO_TOOLS"": "true",
configUSE_MOCKS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

All four hints declared on every tool

18/18 tools missing one or more hints — delete-automation (missing: destructiveHint, idempotentHint, openWorldHint); update-automation-by-entity-id (missing: destructiveHint, idempotentHint, openWorldHint); update-rest-automation-by-rest-id (missing: destructiveHint, idempotentHint, openWorldHint), +15 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 test coverage

Only 1/18 tools referenced in tests (6%)

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

Production dependencies are patched

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

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

Dev dependencies

2 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 4 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/sergiolopezgsiot/aha-mcp?variant=verified)](https://m8ven.ai/mcp/sergiolopezgsiot/aha-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 67f1ab3303317710baad4bbd463214c2723ef84d
code hash: b3acbf17f3fbea01504bfb60a8ba2bc79ab0e6c36b31e3a383f46dab73a3ebc0
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