Home / MCP registry index / io.github.alessandropeng/arc-flash-platform

Arc Flash Platform — Estudos Elétricos

io.github.alessandropeng/arc-flash-platform in the official MCP registry. Endpoint https://arc-flash-platform.onrender.com/mcp.

The registry describes it as: Cálculos de engenharia elétrica pela norma brasileira (NBR), validados, com citação normativa.

We read its 21 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

listar_ferramentas calcular_energia_incidente calcular_energia_incidente_hv calcular_curto_circuito montar_rede tempo_de_atuacao listar_dispositivos gerar_memorial solicitar_orcamento dimensionar_cabo verificar_seccionamento corrigir_fator_potencia dimensionar_tc partida_motor elevacao_temperatura_painel puxamento_cabo grupo_gerador dano_transformador tempo_partida_motor dessintonia_capacitor k_factor_transformador

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-alessandropeng-arc-flash-platform/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-alessandropeng-arc-flash-platform)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.