Real-time Fronius inverter data in Claude — PV, battery, grid and smart meter via local Solar API.
Real-time solar data from your Fronius inverter, directly in Claude. "How much solar power am I generating right now?" "What's my battery charge level?" "Am I currently importing or exporting to the grid?" "How much energy did I produce this year?" "What can you do with my solar system?" "Analyse my photovoltaics for me." Connects to the Fronius Solar API v1 directly on your local network — no…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Real-time solar data from your Fronius inverter, directly in Claude. "How much solar power am I generating right now?" "What's my battery charge level?" "Am I currently importing or exporting to the grid?" "How much energy did I produce this year?" "What can you do with my solar system?" "Analyse my photovoltaics for me." Connects to the Fronius Solar API v1 directly on your local network — no cloud account, no subscription, no data leaving your home. fronius-mcp is a Model Context Protocol…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.