MCP server for Aruba Central: expose AP, switch, and client status to AI assistants
MCP server for Aruba Central (GreenLake New Central API). Exposes access point, switch, and wireless client status to MCP-compatible AI assistants (Claude Code, Claude Desktop, etc.) via STDIO transport. ------|-------------| | List all access points (with optional site/status filter) | | List AP radios (channel, utilization, noise floor, TX power) | | List WLANs (SSID, security, VLAN) | | List…
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”.
MCP server for Aruba Central (GreenLake New Central API). Exposes access point, switch, and wireless client status to MCP-compatible AI assistants (Claude Code, Claude Desktop, etc.) via STDIO transport. ------|-------------| | List all access points (with optional site/status filter) | | List AP radios (channel, utilization, noise floor, TX power) | | List WLANs (SSID, security, VLAN) | | List AP swarms/clusters | | Get detailed status of a specific AP | | Get AP throughput trend (TX/RX over…
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.