Back to MCP Trust Indexm8ven
F
Warning
31/100
3 days ago

hpe-networking-mcp

Low-token MCP server for HPE Networking automation, enabling search of Aruba/HPE docs, OpenAPI details, Central health checks, troubleshooting workflows, configuration management, and guarded ArubaOS 8 migrations and GreenLake Platform operations across platforms like Aruba Central, ClearPass, Mist, and Apstra.

→ secure-ssid/hpe-networking-mcp· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

secure-ssid

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: EDGECONNECT_AI_SESSION_AUTHORIZATION. We can’t prove the destination matches the brand the credential belongs to.
🚨
Reads files from sensitive locations
Touches: credentials.yaml, credentials.yaml
🔐
You'll be asked for 13 credentials: AOS8_API_TOKEN, AOS8_PASSWORD, APSTRA_PASSWORD, APSTRA_API_TOKEN, AXIS_API_TOKEN, CLEARPASS_API_TOKEN, EDGECONNECT_API_TOKEN, MIST_API_TOKEN, MIST_CSRF_TOKEN, MCP_HTTP_BEARER_TOKEN, UXI_CLIENT_SECRET, POSTMAN_API_KEY, GITHUB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHPE_MCP_ROUTER_MODE
configHPE_MCP_NORMALIZE_MACS
configAOS8_BASE_URL
🔐 secretAOS8_API_TOKEN
configAOS8_USERNAME
🔐 secretAOS8_PASSWORD
configAOS8_CLIENT_IP
configAOS8_SESSION_TTL_SECONDS
configAPSTRA_BASE_URL
configAPSTRA_USERNAME
🔐 secretAPSTRA_PASSWORD
🔐 secretAPSTRA_API_TOKEN
configAXIS_BASE_URL
🔐 secretAXIS_API_TOKEN
configCLEARPASS_BASE_URL
🔐 secretCLEARPASS_API_TOKEN
configCREDS_PATH
configEDGECONNECT_BASE_URL
🔐 secretEDGECONNECT_API_TOKEN
configEDGECONNECT_AUTH_HEADER
configEDGECONNECT_ALLOW_LEGACY_API
configGLP_GENERATED_REGION
configHPE_MCP_GLP_GENERATED_TOOLS
configHPE_MCP_TOOLSETScentral,glp,rag
configMIST_HOST
🔐 secretMIST_API_TOKEN
configMIST_SESSION_COOKIE
🔐 secretMIST_CSRF_TOKEN
configHPE_MCP_PRODUCT_ACCESS
configMCP_TRANSPORT
configMCP_HOST
configMCP_PORT8010 bash scripts/run_http_router.sh
configHPE_MCP_READONLY
configHPE_MCP_RAG_BACKEND
🔐 secretMCP_HTTP_BEARER_TOKEN. See [MCP client recipes](docs/mcp-client-recipes.md)
configUXI_CLIENT_ID
🔐 secretUXI_CLIENT_SECRET
configUXI_BASE_URL
configUXI_TOKEN_URL
configHPE_MCP_DIAGRAM_ICON_DIR
configHPE_MCP_DIAGRAM_ALLOW_LARGE_ICONS
configHPE_MCP_PRODUCTSclearpass,mist,apstra,aos8,edgeconnect,uxi,axis,design
🔐 secretPOSTMAN_API_KEY
🔐 secretGITHUB_TOKEN
configHPE_MCP_CENTRAL_WRITES
configHPE_MCP_ACCESS_PROFILEcustom preserves the current per-platform behavior; use safe-read-only to block every write or full-read-write to enable ordinary writes on every loaded platform.
configMCP_ALLOWED_HOSTSexplicit /MCP_ALLOWED_ORIGINS and can be protected with
configMCP_ALLOWED_ORIGINSexplicit MCP_ALLOWED_HOSTS/ and can be protected with
configGLP_TOKEN_URL
configGITHUB_ACTIONS
configGITHUB_WORKFLOW
configGITHUB_RUN_ID
configGITHUB_RUN_ATTEMPT
configGITHUB_REPOSITORY
configGITHUB_REF
configGITHUB_SHA
configHPE_MCP_EMBED_PROVIDERS
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

609/609 tools missing one or more hints — find_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); invoke_read_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); invoke_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +606 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

476/609 tools referenced in tests (78%)

Write tests that reference each tool by name so every tool has at least one test.

No access to sensitive paths

Reads sensitive paths: credentials.yaml, credentials.yaml

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (EDGECONNECT_AI_SESSION_AUTHORIZATION → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/secure-ssid-hpe-networking-mcp-x8npqw?variant=verified)](https://m8ven.ai/mcp/secure-ssid-hpe-networking-mcp-x8npqw)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2db7d458af3318f965452afebd252c31d226dfca
code hash: 8ef74b0228a40cfb72b6714ec84cfd5633f8cad6f003598d2b9a7b87bb5d7927
verified: 8/16/2026, 9:04:26 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client