ai-driven-network-remediation (rh-ai-quickstart/ai-driven-network-remediation) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
2 days ago

ai-driven-network-remediation

AI-driven network operations solution for distributed edge infrastructure.

→ rh-ai-quickstart/ai-driven-network-remediation· listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

rh-ai-quickstart

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 8 credentials: SERVICENOW_PASSWORD, AAP_TOKEN, GITEA_TOKEN, LOKI_TOKEN, SLACK_BOT_TOKEN, LIGHTSPEED_TOKEN, MINIO_ACCESS_KEY, MINIO_SECRET_KEY
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.
configVITE_CHATBOT_URL
configVITE_RAN_CHATBOT_URL
configAPP_TITLE
configSERVICENOW_USERNAME
🔐 secretSERVICENOW_PASSWORD
configAUTO_INGEST_ON_STARTUP
configMCP_PORT
configMCP_HOST
configAAP_URL
configAAP_API_PREFIX
🔐 secretAAP_TOKENBy default, make helm-install deploys an AAP mock. To use a real AAP controller, set ENABLE_AAP_MOCK=false and provide an OAuth2 token via or reference a pre-existing secret via AAP_SECRET_NAME.
configAAP_VERIFY_SSL
configAAP_CA_BUNDLE
configGITEA_URL
configGITEA_OWNER
configGITEA_REPO
configGITEA_TOKEN_PATH
🔐 secretGITEA_TOKEN
configKAFKA_BOOTSTRAP
configKAFKA_CONSUME_TOPICS
configKAFKA_PRODUCE_TOPICS
🔐 secretLOKI_TOKEN
configLOKI_TOKEN_PATH
configLOKI_TLS_VERIFY
configLOKI_CA_CERT_PATH
configLOKI_DEFAULT_TENANT
configLOKI_MAX_LINES
configLOKI_MAX_LINES_CEILING
configLOKI_MAX_DURATION
configLOKI_QUERY_TIMEOUT
configLOKI_RETRY_ATTEMPTS
configEDGE_KUBECONFIG
configKUBECONFIG_DIR
configSPOKE_NAME_PREFIX
configDEPLOYMENT_MODE
configDEFAULT_NAMESPACE
configSERVICENOW_URL
configSERVICENOW_CALLER_NAME
🔐 secretSLACK_BOT_TOKEN
configSLACK_NOC_CHANNEL
configCLUSTER_COUNTSingle-cluster and ACM hub-spoke orchestration use make acm-deploy (=1 or >=2). See the [Multi-cluster deployment guide](docs/multi-cluster-deploy.md).
configEDGE_NAMESPACE
configMULTI_CLUSTER_CREDS_SA
configEDGE_DEPLOYMENT
configEDGE_SITE_ID
configEDGE_MEMORY_REQUEST
configEDGE_MEMORY_LIMIT
configEDGE_COOLDOWN_SECONDS
configEDGE_LABEL_SELECTOR
configEDGE_RUNNER_URL
configEDGE_UNSAFE_MEMORY_LIMIT_MI
configEDGE_POLL_INTERVAL_SECONDS
configKAFKA_GROUP_ID
configKAFKA_AUDIT_TOPIC
configGRAPH_INVOKE_TIMEOUT_SECONDS
configLLAMASTACK_HOST
configLLAMASTACK_PORT
configVECTOR_STORE_NAME
configVECTOR_STORE_CHUNK_SIZE_TOKENS
configVECTOR_STORE_CHUNK_OVERLAP_TOKENS
configGRANITE_MODEL_NAME
configLIGHTSPEED_URL
🔐 secretLIGHTSPEED_TOKEN
configLIGHTSPEED_VERIFY_SSL
configGITEA_PROJECT_NAME
configLIGHTSPEED_TIMEOUT_SECONDS
configLIGHTSPEED_MAX_SUMMARIZE_CHARS
configSLACK_CHANNEL
configSLACK_TIMEOUT_SECONDS
configSERVICENOW_INSTANCE_URL
configFAST_PATH_COOLDOWN_SECONDS
configINVESTIGATE_MAX_ITERATIONS
configMCP_OPENSHIFT_URL
configMCP_LOKISTACK_URL
configMCP_KAFKA_URL
configMCP_AAP_URL
configMCP_SERVICENOW_URL
configMODEL_API_URL
configMODEL_NAME
configMODEL_TIMEOUT_SECONDS
configMODEL_MAX_TOKENS
configDEMO_TOPIC
configAUDIT_TOPIC
configAUDIT_LOOKBACK_HOURS
configAUDIT_MAX_MESSAGES
configINTEGRATIONS_CACHE_TTL
configBASELINE_MANUAL_MTTR_SECONDS
configOPS_HOURLY_COST_USD
configCORS_ORIGINS
configSSL_CA_BUNDLE
configEMBEDDING_MODEL
configCHUNK_SIZE_TOKENS
configCHUNK_OVERLAP_TOKENS
configRUNBOOKS_DIR
configMINIO_ENDPOINT
🔐 secretMINIO_ACCESS_KEY
🔐 secretMINIO_SECRET_KEY
configMINIO_BUCKET
configMINIO_RUNBOOK_PREFIX
configTELCO_DOCS_DIR
configTELCO_VECTOR_STORE_NAME
configMINIO_TELCO_DOCS_PREFIX
configKAFKA_METRICS_TOPIC
configKAFKA_ANOMALIES_TOPIC
configHISTORY_WINDOW_SIZE
configRECENT_ANOMALIES_LIMIT
configENRICHED_ANOMALIES_TOPIC
configENRICHED_ANOMALIES_MAX_MESSAGES
configDEMO_METRICS_TOPIC
configKAFKA_ENRICHED_TOPIC
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

29/29 tools missing one or more hints — list_job_templates (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); launch_job (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); upsert_job_template (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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.

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 2 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 Score](https://m8ven.ai/badge/mcp/rh-ai-quickstart-ai-driven-network-remediation-0zmubd)](https://m8ven.ai/mcp/rh-ai-quickstart-ai-driven-network-remediation-0zmubd)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 34e6983389983d243277a1219239bfae48837517
code hash: 2183f61c6192e553c694658308e45541450e9c51913d672c1ada7262b7369c02
verified: 9/2/2026, 7:10:52 PM
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