pulsemcp scanned Safe content atomic mcp-remote

Enhanced Home Assistant

An enhanced Home Assistant MCP server built by gilberth that provides comprehensive smart home automation control through a rich set of tools for managing entities, devices, automations, history analysis, and system monitoring. The implementation features domain-specific device controls for lights, climate, media players, and covers with advanced parameters, bulk operations for managing multiple entities simultaneously, detailed historical analysis with state change tracking, and resource-based URI access patterns for efficient data retrieval. Built with TypeScript and designed for Smithery compatibility, it includes minimal tool registration to prevent timeout during scanning, extensive filtering and search capabilities across all entity operations, and specialized tools for troubleshooting, configuration validation, and system health monitoring, making it useful for AI-assisted home automation management, energy optimization analysis, and comprehensive smart home system administration.

Cognium trust score

84%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: iot-hardware
Source: PulseMCP
Repository: github.com/gilberth/enhanced-homeassistant-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Enhanced Home Assistant from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"