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

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

chronos-graph

AIエージェントの「健忘症（ステートレス性）」を解決し、長期的な記憶保持と自己進化を実現するためのプラグイン・フレームワークです。

→ yohi/chronos-graph· 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

yohi

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.
✅
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 4 credentials: MCP_GATEWAY_API_KEY, SUPABASE_KEY, TEST_DB_PASSWORD, TEST_NEO4J_PASSWORD
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.
configMCP_HOOK_MAX_LOG_BYTESフック経由送信の最大ログサイズ（超過時は末尾保持で切り詰め）
configMCP_GATEWAY_URLagent_turn_hook.py から到達する ChronosGate URL
🔐 secretMCP_GATEWAY_API_KEYagent_turn_hook.py が ChronosGate へ送る Bearer 相当の API キー
configMCP_INTENT
configMCP_HOOK_TIMEOUT_SECONDSagent_turn_hook.py の全体ハードリミットタイムアウト（秒）
configMCP_HOOK_SSE_TIMEOUT_SECONDSagent_turn_hook.py の SSE ハンドシェイクタイムアウト（秒）
configLOG_LEVEL
configENV_FILE
configSUPABASE_URLSupabase プロジェクト URL
🔐 secretSUPABASE_KEYSupabase Service Role Key (機密情報のため厳重管理)
configSQLITE_DB_PATH
configPROJECT_ROOT
configTEST_DB_HOST
configTEST_DB_PORT
configTEST_DB_NAME
configTEST_DB_USER
🔐 secretTEST_DB_PASSWORD
configTEST_NEO4J_URI
configTEST_NEO4J_USER
🔐 secretTEST_NEO4J_PASSWORD
configTEST_REDIS_URL
configOPENSANDBOX_URL
configCODEX_HOME
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
deployDATABASE_URL
// 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

8/8 tools missing one or more hints — session_flush (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_save (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_save_url (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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/yohi/chronos-graph)](https://m8ven.ai/mcp/yohi/chronos-graph)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a0d53ed2ca61b3e4fece47354d2a7c320dfe5c6a
code hash: 8b515fb7fbdf6ef8bcad1cd45adbf7f8e1dba7702211978e734a62f06a5c1fb4
verified: 9/2/2026, 10:57:48 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