HA Admin MCP (paulcakeface/ha-admin-mcp) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
69/100

HA Admin MCP

An MCP server for safely previewing, creating, validating, editing and rolling back AI-managed Home Assistant automations.

→ paulcakeface/ha-admin-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

paulcakeface

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: MCP_CLIENT_TOKEN, HA_TOKEN, HA_INTEGRATION_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
🔐 secretMCP_CLIENT_TOKENPut the generated value in . Do not reuse the Home
configLOG_LEVELApplication log level INFO
configHA_URLSet to a Home Assistant address reachable from the container.
🔐 secretHA_TOKENSet to a Home Assistant long-lived access token.
configMCP_ISSUER_URLStatic-auth issuer identifier; use the public base URL remotely http://127.0.0.1:8765
configHA_AUTOMATIONS_FILEAI automation file inside the container /ha-ai/ai_automations.yaml
configBACKUP_DIRBackup directory inside the container /data/backups
configLOG_DIRAudit-log directory inside the container /data/logs
configMCP_HOSTListen address inside the container 0.0.0.0
configMCP_PORTListen port inside the container 8000
configHA_ADMIN_MCP_URL
configHA_INTEGRATION_URLexport ='http://homeassistant:8123'
🔐 secretHA_INTEGRATION_TOKENexport ='your-test-token'
// 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

15/15 tools missing one or more hints — ha_health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_ai_automations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_ai_automation (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 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

10/15 tool handlers declare input schemas (67%)

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

Tool handlers catch errors

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

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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 5 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 Score](https://m8ven.ai/badge/mcp/paulcakeface/ha-admin-mcp)](https://m8ven.ai/mcp/paulcakeface/ha-admin-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 366acf020c6c242a9a776cbc59941a3dcbd7eed9
code hash: 17650fb319283ed0feaafda0a2ca12de8ff5f0d14b0a38223e3f87a35ebb1fed
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