Aruba Central MCP
PYPI · ARUBA-CENTRAL-MCP
MCP server for Aruba Central: expose AP, switch, and client status to AI assistants
Available components
Last scanned (4 hours ago)
Scores higher than 90% of PyPI servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shigechika/aruba-central-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2527 tokens (~140/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (94% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −4
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.67 functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.10.1 → 0.10.2 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Schema quality: 118 → 140 ▼ functional
- Schema quality: 118 → 134 ▼ functional
- Package version: 0.9.0 → 0.10.1 functional
- Package version: 0.9.0 → 0.10.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/aruba-central-mcp@0.10.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | shigechika/aruba-central-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shigechika/aruba-central-mcp/.github/workflows/release.yml@refs/tags/v0.10.2 |
| Rekor log index | 3500400800 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:a618ca6c7b9009abfb8f77d32ba96ba8765e387fcce0055ebc23918c57bfb02e |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
daily_brief ~190
Run a morning AP health check across all sites. Fetches all access points and aggregates their online/offline status by site. Sites whose offline AP ratio is *strictly greater than* ``offline_threshold`` percent are flagged as WARNING (uses ``>``, so a site with exactly ``offline_threshold`` % offline is still OK). Args: offline_threshold: Percentage of offline APs that triggers a WARNING (default 10.0). Sites at or below this threshold appear in the OK section. Pass 0.0 to flag any site with at least one offline AP. Output tiers: - CRITICAL — API connection failure - WARNING — offline AP ratio strictly above threshold - OK — offline ratio at or below threshold Returns a Markdown summary with site-level AP counts and anomaly details.
| Name | Type | Req | Description |
|---|---|---|---|
| offline_threshold | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
find_client_by_mac ~83
Look up a single client by MAC address (wireless or wired). Returns detailed info including OS, manufacturer, VLAN, and connection status. Uses direct API lookup (no full-list scan). Args: mac_address: Client MAC address (e.g. "aa:bb:cc:dd:ee:ff").
| Name | Type | Req | Description |
|---|---|---|---|
| mac_address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
firmware_status ~430
Firmware of every AP swarm (cluster): running versions, upgrade status, group and site. Use this to see which swarms still need a firmware upgrade and what Central will do next. Read-only. The whole call is bounded (about 48 s); what could not be read in time is named under Notes. One line per swarm with its group(s) and site(s), AP count and how many are online, the running versions with AP counts, the recommended version and New Central's per-AP upgrade status (/network-services/v1/firmware-details). APs that belong to no swarm are listed per group and site. When Classic Central is configured (ARUBA_CLASSIC_*), each swarm also gets its Classic group, the group's compliance version (the version Central keeps the group's swarms on: an upgrade of a Classic IAP group happens when the compliance version changes, and ``scheduled`` is when that is set to run; a site-level upgrade in the UI does not change it), marked "matches running" or "pending", and "older than ..." when it is lower than the running or recommended version, plus Classic's upgrade ``state``, ``reason`` and ``upgrade_required``. New Central reports no group for AOS-8 APs, so the group comes from Classic; Classic data is cached per group for a few minutes. Swarms Classic knows but New Central does not (e.g. 0 APs, Down) are listed at the end when no site or swarm filter is given. A Classic failure is reported under Notes; the New Central data is still shown. Filters combine (all must match); each is an exact name, case-insensitive. Empty means no filter. ``group`` uses the Classic group when New Central has none. Args: group: Central group name. site: Site name. swarm_name: Swarm (cluster) name.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | – |
| site | string | – | – |
| swarm_name | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ap_status ~42
Get detailed status of a specific access point by name. Args: ap_name: AP device name (case-insensitive).
| Name | Type | Req | Description |
|---|---|---|---|
| ap_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ap_throughput ~160
Get throughput trend for a specific AP as a time-series table. Returns timestamped TX/RX throughput in bps. Defaults to last 3 hours. Args: serial_number: AP serial number (use list_aps or get_ap_status to find it). interface_type: "WIRELESS" (Wi-Fi), "WIRED" (Ethernet uplink), or "LTE". start_at: Start time in RFC 3339 format. Defaults to 3 hours ago. end_at: End time in RFC 3339 format. Defaults to current time.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | – | – |
| interface_type | string | – | – |
| serial_number | string | yes | – |
| start_at | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_client_mobility_trail ~147
Get roaming history for a wireless client as a time-series table. Shows which APs the client connected to, when, and on which SSID. Useful for troubleshooting connectivity issues or tracking movement. Defaults to last 3 hours. Args: mac_address: Client MAC address (e.g. "aa:bb:cc:dd:ee:ff"). start_at: Start time in RFC 3339 format. Defaults to 3 hours ago. end_at: End time in RFC 3339 format. Defaults to current time.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | – | – |
| mac_address | string | yes | – |
| start_at | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_clients_trend ~249
Get client count trend over time, grouped by a chosen dimension. Useful for capacity planning and usage pattern analysis. Args: site_id: Filter by site ID. Empty for all. site_name: Filter by site name. Empty for all. start_at: Start time in RFC 3339 format (max 1 month range). Must not be in the future. end_at: End time in RFC 3339 format. Must not be in the future. group_by: Dimension to group by. Supported values: - Any client_type: TYPE, ROLE, VLAN - WIRELESS only: WLAN, RADIO, SECURITY, PROTOCOL Default is TYPE. client_type: Client category: ALL, WIRELESS, or WIRED. Default is ALL. Must be WIRELESS when group_by is WLAN, RADIO, SECURITY, or PROTOCOL (the API returns 400 otherwise).
| Name | Type | Req | Description |
|---|---|---|---|
| client_type | string | – | – |
| end_at | string | – | – |
| group_by | string | – | – |
| site_id | string | – | – |
| site_name | string | – | – |
| start_at | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_site_summary ~52
Get a summary of all sites with AP and client counts. Aggregates data across all APs and clients, grouped by site name. Shows total APs, online/offline counts, and client count per site.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_top_aps ~215
Get top access points ranked by bandwidth usage over a time range. Returns a ranked list of APs sorted by descending bandwidth consumption. Args: usage_type: "wireless" (Wi-Fi traffic), "wired" (uplink traffic), or "total" (wireless + wired combined). Default: "total". site_id: Filter by site ID. Empty for all sites. limit: Maximum number of APs to return (1-25, default 10). start_at: Start time in RFC 3339 format (e.g. "2025-01-01T00:00:00Z"). Max 30 days range. Defaults to 24 hours ago if omitted. end_at: End time in RFC 3339 format. Defaults to current time if omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | – | – |
| limit | integer | – | – |
| site_id | string | – | – |
| start_at | string | – | – |
| usage_type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_top_clients_by_usage ~136
Get top clients ranked by bandwidth usage. Args: site_id: Filter by site ID. Empty for all. site_name: Filter by site name. Empty for all. start_at: Start time in RFC 3339 format (max 1 month range). end_at: End time in RFC 3339 format. limit: Maximum number of clients to return (1-100, default 5).
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | – | – |
| limit | integer | – | – |
| site_id | string | – | – |
| site_name | string | – | – |
| start_at | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
health_check ~247
Report server version and Aruba Central backend authentication. Call this at session start (or after a tool-call timeout) to confirm the MCP is up, see which version is running, and verify the Aruba Central backend can be authenticated. Lightweight: it builds the client and obtains an OAuth2 access token (GreenLake SSO, reusing the cached token) — it does NOT fetch APs, switches, clients, or any other data endpoint. Always returns the same keys: ``status`` (healthy / degraded / error), ``service``, ``version``, ``base_url`` (the configured ARUBA_CENTRAL_BASE_URL, empty string if unset), ``auth`` (ok / error / missing-env) and ``classic`` (not-configured / ok / error / misconfigured: the optional Classic Central token used by the firmware tools; ``misconfigured`` means some ARUBA_CLASSIC_* variables are set and others are not). ``error`` and ``misconfigured`` make the status degraded and add ``classic_detail``. On a degraded or error result, ``detail`` carries the reason (the New Central one first when both fail).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_aps ~98
List access points with device-level overview. Use this for AP inventory and availability checks. For RF details (channel, utilization, noise floor), use list_radios instead. Args: site: Filter by site name (exact match, server-side). Empty for all. status: Filter by status (e.g. "ONLINE", "OFFLINE"). Empty for all.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_bssids ~78
List all BSSIDs (per-radio, per-SSID broadcast identifiers). Useful for identifying which radio on which AP is broadcasting a specific SSID. Each AP radio broadcasts one BSSID per WLAN. Args: site: Filter by site name (exact match, server-side). Empty for all.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_clients ~108
List connected wireless clients with connection details. Returns client name, MAC, IP, SSID, band, SNR, connected AP, and auth type. For a single client's full details, use find_client_by_mac instead. Args: ssid: Filter by SSID name (exact match, server-side). Empty for all. band: Filter by wireless band (exact match, server-side). Empty for all.
| Name | Type | Req | Description |
|---|---|---|---|
| band | string | – | – |
| ssid | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_radios ~107
List AP radios with RF details. Use this for RF troubleshooting: channel assignment, channel utilization, noise floor, and TX power. Each AP typically has 2-3 radios (one per band). Args: site: Filter by site name (exact match, server-side). Empty for all. band: Filter by band (e.g. "2.4 GHz", "5 GHz"). Empty for all.
| Name | Type | Req | Description |
|---|---|---|---|
| band | string | – | – |
| site | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_swarms ~64
List all AP swarms (clusters) from Aruba Central. Returns cluster name, conductor AP, site, IP, and firmware version. Args: site: Filter by site name (exact match, server-side). Empty for all.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_switches ~34
List all switches from Aruba Central. Returns switch name, status, model, type, IP, firmware, and MAC address.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_wlans ~87
List configured WLANs (SSIDs) with security and VLAN settings. Shows each WLAN's name, band, operational status, security level, and VLAN assignment. Args: site_id: Filter by site ID. Empty for all. serial_number: Filter by AP serial number. Empty for all.
| Name | Type | Req | Description |
|---|---|---|---|
| serial_number | string | – | – |
| site_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Aruba Central MCP server?
Aruba Central MCP runs locally as a PyPI package, launched with uvx aruba-central-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · aruba-central-mcp
claude mcp add shigechika-aruba-central-mcp -- uvx aruba-central-mcp
What is the Aruba Central MCP server?
Aruba Central MCP is listed in the public MCP registry as io.github.shigechika/aruba-central-mcp. MCP server for Aruba Central: expose AP, switch, and client status to AI assistants. This page covers its PyPI package (aruba-central-mcp).
Is the Aruba Central MCP server safe to use?
Aruba Central MCP scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Aruba Central MCP server expose?
Aruba Central MCP exposes 18 tools: health_check, list_aps, list_switches, list_clients, find_client_by_mac, and 13 more. Their descriptions and schemas cost roughly 2,527 tokens of context every time the server is loaded.
Is the Aruba Central MCP server still maintained?
Aruba Central MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Aruba Central MCP server under?
Aruba Central MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.