kai (Aurite-ai/kai) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

Caution

74/100

kai

Item: kai
Rating: 74
Author: M8ven

🧠 Kai is a context engineering platform. It's persistent memory for AI coding copilots. Teach it once, surface context automatically. MCP server for Claude Code.

→ Aurite-ai/kai · listed on github_repo_search

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 push why connect →

Who stands behind it

Aurite-ai

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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

1 flow detected: PERPLEXITY_API_KEY. We can’t prove the destination matches the brand the credential belongs to.

🚨

Known vulnerabilities in dependencies: 1 critical, 1 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

🔐

You'll be asked for 4 credentials: KAI_USAGE_API_KEY, PERPLEXITY_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// tools this server exposes17 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

kai_ask

Quick Q&A using the project knowledge base. USE THIS TOOL WHEN: - Mid-task and need specific information - User asks a direct question about the project - Need clarification on a decision or pattern - Need information beyond what's in .kai/context-guide.md Searches the knowledge base and synthesiz…

kai_delete

Delete files from the Kai knowledge base. ⚠️ IMPORTANT: This tool should ONLY be called after: 1. kai_learn reports contradictions with existing files 2. You ask the user for permission to delete the outdated files 3. The user explicitly approves the deletion USE THIS TOOL WHEN: - kai_learn output…

kai_discover_integration

Discover and add a new integration connector for any service, API, or tool. Use this when: - The user needs an integration that isn't in the built-in list - The user mentions a specific service (e.g., "I need Twilio", "Add Airtable") - Setting up a new project that requires custom integrations The…

health_check

Check if the Kai MCP server is running correctly. This tool verifies the MCP connection is working. Actions: - ping: Confirm MCP server is alive

kai_initialize

Deploy agent-dev rules and optionally run onboarding to collect org/user context. USE THIS TOOL WHEN: - User says "set up Kai", "initialize", "get started with Kai" - Starting to use Kai in a new project - User wants to configure their copilot with Kai integration This tool does TWO things: 1. Dep…

kai_learn

Send files or folders to Kai to learn from and add to the knowledge base. USE THIS TOOL WHEN: - User shares files/folders and wants Kai to "learn" from them - User provides policy documents, specs, or reference materials - User says "here's our...", "learn this", "add this to context" - After compl…

kai_list_integrations

List all discovered integrations and their status. Use this tool to see what integrations are available for use. Shows integration names, types, available operations, and current status (discovered, configured, verified, error). Use this before kai_use_integration to know what integrations are av…

kai_prepare_context

Prepare the .kai/context-guide.md with relevant knowledge for a task. USE THIS TOOL WHEN: - Starting any new task or feature - User describes what they want to build - Before beginning implementation work - User asks "what do we know about X" This is the PRIMARY context retrieval tool. Call it ONC…

kai_provide_context

Store org or user context in the knowledge base. USE THIS TOOL WHEN: - Completing onboarding (storing synthesized org or user context) - User describes their organization, preferences, or constraints - Synthesizing context from a conversation (without creating temp files) This tool stores free-for…

kai_update_connector

Update or refresh an existing integration connector. Use this when: - API endpoints have changed and need refreshing - Adding new operations to an existing connector - Fixing authentication issues discovered during verification - Updating rate limit or base URL information - Refreshing a connector …

kai_usage

View token usage and cost summary for the current project. USE THIS TOOL WHEN: - User asks about usage, costs, or token consumption - User wants to see how much they've spent - User asks "how much have I used?" Shows cumulative project totals and breakdown by tool. <examples> ### Check usage kai_…

kai_use_integration

Execute an operation on a discovered integration. Use this tool to interact with external services (APIs, databases, etc.) that Kai has learned about. The integration must first be discovered using kai_learn on files that describe it. Examples: - Query a database: integration="postgresql", operat…

kai_verify_integration

Verify that an integration is correctly configured and can connect. Use this tool to test if an integration is working before using it. Checks that credentials are available and attempts a simple operation to verify connectivity. Can verify a single integration or all discovered integrations.

add

Add two numbers together.

subtract

Subtract the second number from the first.

multiply

Multiply two numbers together.

divide

Divide the first number by the second.

// known CVEs in dependencies1 critical1 high3 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.1.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

lowyaml@2.4.0GHSA-48c2-rrv3-qjmp

yaml is vulnerable to Stack Overflow via deeply nested YAML collections

lowesbuild@0.27.3GHSA-g7r4-m6w7-qqqr

esbuild allows arbitrary file read when running the development server on Windows

lowvitest@3.1.0GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// 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.

configENABLE_PERPLEXITY_INTEGRATION

configKAI_INCLUDE_USAGE_IN_RESPONSES

configKAI_KNOWLEDGE_DIR

configKAI_ORG_ID

configKAI_TEAM_ID

configKAI_TEMPLATES_DIR

configKAI_USAGE_API_ENDPOINT

🔐 secretKAI_USAGE_API_KEY

configKAI_USER_ID

🔐 secretPERPLEXITY_API_KEY

🔐 secretANTHROPIC_API_KEYKai requires an for AI-powered tools. Set it in your MCP config:

🔐 secretOPENAI_API_KEY

// 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

17/17 tools missing one or more hints — kai_ask (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); kai_delete (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); kai_discover_integration (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

7/17 tools referenced in tests (41%)

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

Shell command execution

11 calls in production code run through a shell (src/vault/1password-provider.ts:171, src/vault/1password-provider.ts:176, src/vault/1password-provider.ts:230)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high), yaml@2.4.0 (low)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 7 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/aurite-ai/kai?variant=verified)](https://m8ven.ai/mcp/aurite-ai/kai)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: c4d0b06f552c4ce1f41c5acad24c661b6e577db8

code hash: 3729003895a7ca3abe9610011d109de79ac3b28ce805e597fc7575f294476500

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