kagent (kagent-dev/kagent) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 19 tools. No publisher has claimed this listing.

A
Trusted
98/100

kagent

Cloud Native Agentic AI | Discord: https://bit.ly/kagentdiscord

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

kagent-dev

Source: github_repo_search

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

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
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 7 credentials: KAGENT_PROPAGATE_TOKEN, OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, GEMINI_API_KEY, AZURE_OPENAI_API_KEY, SAP_AI_CORE_CLIENT_SECRET
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.
configKAGENT_DEV_CONTROLLER_URL
configUI_LOOP_EXTENSION_PORT
configUI_LOOP_LIVE
configUI_LOOP_LIVE_PORT
configUI_LOOP_PORT
configKAGENT_SKILLS_FOLDER
configKAGENT_A2A_GRPC_ADDRESS
configSTS_WELL_KNOWN_URI
🔐 secretKAGENT_PROPAGATE_TOKEN
configKAGENT_STS_RESOURCE
configKAGENT_STS_AUDIENCE
configUVICORN_LOG_LEVEL
configLOG_LEVEL
configKAGENT_API_URL
configKAGENT_GATEWAY_URL
configKAGENT_NAME
configKAGENT_NAMESPACE
configOTEL_TRACING_ENABLED
configOPENAI_API_BASE
🔐 secretOPENAI_API_KEY
configKAGENT_OPENAI_AGENTS_NATIVE_TRACING
configOPENAI_AGENTS_DISABLE_TRACING
configBASH_VENV_PATH
🔐 secretANTHROPIC_API_KEY
configAWS_DEFAULT_REGION
configAWS_REGION
configOPENAI_API_VERSION
configAZURE_OPENAI_ENDPOINT
configOLLAMA_API_BASE
🔐 secretGOOGLE_API_KEY
🔐 secretGEMINI_API_KEY
🔐 secretAZURE_OPENAI_API_KEY
configSAP_AI_CORE_CLIENT_ID
🔐 secretSAP_AI_CORE_CLIENT_SECRET
configOTEL_EXPORTER_OTLP_PROTOCOL
configOTEL_EXPORTER_OTLP_TIMEOUT
configKAGENT_TRACE_FLUSH_TIMEOUT_MS
configOTEL_LOGGING_ENABLED
configOTEL_EXPORTER_OTLP_TRACES_ENDPOINT
configOTEL_TRACING_EXPORTER_OTLP_ENDPOINT
configOTEL_EXPORTER_OTLP_ENDPOINT
configKAGENT_PRE_RESPONSE_TRACE_FLUSH
configOTEL_EXPORTER_OTLP_LOGS_ENDPOINT
configOTEL_LOGGING_EXPORTER_OTLP_ENDPOINT
// 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

19/19 tools missing one or more hints — connectionsafemcp (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); kagentremotea2a (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); returnartifacts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 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

6/19 tools referenced in tests (32%)

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/kagent-dev/kagent)](https://m8ven.ai/mcp/kagent-dev/kagent)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a9553f5a6c1f759b86951f3efba0a285c6c67fa9
code hash: 0fec15217d368bcb27d4f18cc0f9147c39d8c0ff04e855712278091191104d99
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