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

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

kimi-core

个人用的 agent memory OS——记忆系统 + self-drive 自主情感，内置对抗式自审 harness。内在过程需要外在标准。

→ marikagura/kimi-core· 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

marikagura

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

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.
🔐
You'll be asked for 9 credentials: COHERE_API_KEY, DATA_PROBE_CONCERN_KEY, EMBED_API_KEY, JINA_API_KEY, KIMI_API_KEY, KIMI_MCP_TOKEN, LLM_API_KEY, SEARCH_API_KEY, VOYAGE_API_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.
configCAL_NAMESPACE
🔐 secretCOHERE_API_KEY
configCONSOLIDATE_CRON
configCORS_ALLOWED_ORIGINS
configCURATION_REVIEW_THRESHOLD
configDAEMON_WAKE_CRON
🔐 secretDATA_PROBE_CONCERN_KEY
configDEMO_FEED_CRON
configDEPTH_TOPIC_SLUG
configDRIVE_DIMS
🔐 secretEMBED_API_KEY
configEMBED_BASE_URL
configEMBED_MODEL
configEVAL_WRITE_EVENT
configINTEL_DAILY_CRON
configINTEL_DIGEST_CRON
configINTEL_TOPIC_CRITERION
configINTEL_TOPIC_SLUG
🔐 secretJINA_API_KEY
🔐 secretKIMI_API_KEY
configKIMI_CRON_TZ
configKIMI_EXTENSIONS
🔐 secretKIMI_MCP_TOKEN
configKIMI_MCP_URL
configKIMI_MODEL
🔐 secretLLM_API_KEY
configLLM_BASE_URL
configLLM_PROVIDER_ORDER
configLLM_SHORT_MODEL
configNOTIFIER
configNOTIFIER_WEBHOOK_FIELD
configNOTIFIER_WEBHOOK_URL
configPAPER_LOOP_CRON
configPERSONA_PATH
configRERANK_LOCAL_URL
configRERANK_MODEL
configRERANK_PROVIDER
🔐 secretSEARCH_API_KEY
configSEARCH_API_URL
configSEARCH_FIELD_SNIPPET
configSEARCH_FIELD_TITLE
configSEARCH_FIELD_URL
configSEARCH_PROVIDER
configSEARCH_QUERY_PARAM
configSEARCH_RESULTS_PATH
configTHOUGHT_SOURCE_WEIGHTS
🔐 secretVOYAGE_API_KEY
configWEEKLY_ARC_CRON
configRERANK_HOST
configRERANK_MAX_LEN
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

38/38 tools missing one or more hints — closeout (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); entity_write (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); entity_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +35 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.

README present

No README found

Add a README.md describing the server and its tools.

License file

No license file

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

Tool test coverage

Only 9/38 tools referenced in tests (24%)

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 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 Score](https://m8ven.ai/badge/mcp/marikagura/kimi-core)](https://m8ven.ai/mcp/marikagura/kimi-core)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a8fe84102acdf28d57ea62693e4330ab057898ba
code hash: b102b17e9a1337f6791fb31ec6770b54258be2547a721288a7487e93ee5ddbb4
verified: 9/3/2026, 5:46:24 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