kassi-CLI (Vision-Stack20/Kassi-CLI) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 2 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
8 days ago

kassi-CLI

An AI agent that load-tests a code change, finds regression in live Splunk, and writes the fix before it reaches production, all driven through MCP.

→ Vision-Stack20/Kassi-CLI· listed on glama

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

Vision-Stack20

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

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: KASSI_HEC_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: SPLUNK_PASS, ANTHROPIC_API_KEY, KASSI_HEC_TOKEN, KASSI_SPLUNK_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.
configKASSI_FORECASTER
configSPLUNK_MGMT
configSPLUNK_USER
🔐 secretSPLUNK_PASS
configUPSTREAM
configSPLUNK_HEC
configSPLUNK_INDEX
configOLLAMA_HOSTOllama endpoint (point at the host running the local model, e.g. a LAN box)
configKASSI_MODELmodel tag: an Ollama tag, or a Claude model alias/id for the Claude backends
configKASSI_RUN_INDEX
configSPLUNK_HOME
configKASSI_LLMmodel backend: ollama (local), claude_agent (Claude via the Claude Code session, no API key), or anthropic (Claude Messages API)
configUV
configKASSI_GUARDIAN
configKASSI_GUARDIAN_MODEL
configKASSI_NUM_CTX
🔐 secretANTHROPIC_API_KEYClaude API key (only for KASSI_LLM=anthropic; claude_agent uses the logged-in Claude Code session instead)
🔐 secretKASSI_HEC_TOKENand a run-history table. Gated on : with it unset, runs simply don't publish.
configKASSI_HEC_URL
configKASSI_K6_DOCKERif set, run the k6 MCP server via Docker
configKASSI_K6_IMAGEDocker image when KASSI_K6_DOCKER is set
configKASSI_K6_CMDcommand line for the k6 MCP server (set to mcp-k6 for the standalone binary)
configKASSI_SPLUNK_MCP_ENDPOINTThe Splunk step is optional: without + KASSI_SPLUNK_TOKEN, kassi
🔐 secretKASSI_SPLUNK_TOKENThe Splunk step is optional: without KASSI_SPLUNK_MCP_ENDPOINT + , kassi
configKASSI_SPLUNK_MCP_CMDstdio bridge command (runs mcp-remote)
configKASSI_SPLUNK_INSECUREskip TLS verification in the bridge (local self-signed Splunk only)
// 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

2/2 tools missing one or more hints — splunk_run_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); splunk_get_indexes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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

1/2 tools referenced in tests (50%)

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

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 3 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/vision-stack20/kassi-cli)](https://m8ven.ai/mcp/vision-stack20/kassi-cli)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7e4ee42a64a35886e97aff97626a6af766401efd
code hash: 209dd6b6eef8f47a5e5d186f92b783dbfe1ed7f68ea74dee11f3b7fb6fab1fee
verified: 9/4/2026, 3:20:41 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