ariaops-mcp (asnd/ariaops-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Caution
74/100
14 days ago

ariaops-mcp

Read-only MCP server for VMware Aria Operations (on-prem)

Caution. Specific findings reduced this grade. They are listed on the page. 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

asnd

Source: github_code

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 →

Install from

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

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: LITELLM_TOKEN, KEYCLOAK_REALM, KEYCLOAK_BASE_URL. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: LITELLM_TOKEN, ARIAOPS_PASSWORD, KEYCLOAK_PASSWORD
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.
configLITELLM_BASE_URLSet for the gateway. If you want to use the Get Token via Azure SSO button, also set:
configHTTP_PROXY
confighttp_proxy
configHTTPS_PROXY
confighttps_proxy
configNO_PROXY
configno_proxy
🔐 secretLITELLM_TOKENNo — Test UI JWT for the gateway
configAZURE_TENANT_IDyour-azure-tenant-id
configAZURE_CLIENT_IDyour-azure-client-id
configARIAOPS_HOSTvrops.example.com
configARIAOPS_USERNAMEvariables (ARIAOPS_HOST//ARIAOPS_PASSWORD) are optional.
🔐 secretARIAOPS_PASSWORDvariables (ARIAOPS_HOST/ARIAOPS_USERNAME/) are optional.
configARIAOPS_MCP_URLedit .env: set + optional LITELLM_ vars
configARIAOPS_MCP_VERIFY_TLS
configLLM_MODEL
configLITELLM_VERIFY_TLS
configKEYCLOAK_BASE_URL
configKEYCLOAK_REALM
configKEYCLOAK_USERNAME
🔐 secretKEYCLOAK_PASSWORD
configKEYCLOAK_CLIENT_ID
configKEYCLOAK_VERIFY_SSL
configKEYCLOAK_MCP_REALM
configKEYCLOAK_MCP_RESOURCE_SERVER_URL
configKEYCLOAK_MCP_AUDIENCE
configKEYCLOAK_MCP_REQUIRED_SCOPES
configKEYCLOAK_WRITE_ENV_FILE
// 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

62/62 tools missing one or more hints — call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_skills (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_skill (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +59 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.

Secrets stay with their owner

3 secret/sensitive values flow into network calls (LITELLM_TOKEN → dynamic, KEYCLOAK_REALM → dynamic)

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

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

6 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 5 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/asnd-ariaops-mcp-1jnq6v?variant=verified)](https://m8ven.ai/mcp/asnd-ariaops-mcp-1jnq6v)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8ff276ce34811c7797fabdd61fca09f348322632
code hash: f84cf819f5366c2648b03da52afb08abd18b85a412a00a1e98a959acc171f8ab
verified: 8/12/2026, 7:53:27 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