OCD - Organized Context Datastore (MCP) (teamstove/organized-context-datastore-mcp) is an MCP server listed on the M8ven Trust Index. It scores 44 out of 100, grade D. It declares 16 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
44/100

OCD - Organized Context Datastore (MCP)

Give your AI persistent, structured memory and let humans see it too. It stores project knowledge as Markdown files in a hierarchical tree, accessible via MCP tools and a built-in Web UI.

→ teamstove/organized-context-datastore-mcp· listed on glama

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 pushwhy connect →

Who stands behind it

teamstove

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
🚨
Known vulnerabilities in dependencies: 2 critical, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// tools this server exposes16 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.

list_context_roots

Context Root一覧を取得します（cwd から設定を探索）

get_contexts

パターンとフィルタでコンテキストを取得します

get_context_tree

コンテキストツリー(目次)を取得します。rootIds には list_context_roots で取得した id を使用してください。

search_contexts

キーワードでコンテキストを検索します

mutate_context

コンテキストを変更します (create/update/delete/move)

commit

変更をコミットします (draft_commitモード用)

ocd_list_context_roots
ocd_get_contexts
ocd_get_context_tree
ocd_search_contexts
ocd_mutate_context
ocd_commit
create_context

新規コンテキストを作成します (配列対応: 複数一括作成可能)

update_context

既存コンテキストを更新します (配列対応: 複数一括更新可能) ## 概要 メタデータ (title, summary, categories, tags) と コンテンツ (contentUpdates) の両方を更新可能。 ## contentUpdates の操作タイプ ### whole_replace - コンテンツ全置換 { type: 'whole_replace', content: '新しいコンテンツ全体' } ### replace - 部分置換（batch-filesystem-operations と同じ search / replacement / isRege…

delete_context

コンテキストを削除します (配列対応: 複数一括削除可能)

move_context

コンテキストを移動/リネームします (配列対応: 複数一括移動可能)

// known CVEs in dependencies2 critical3 high

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

criticalsimple-git@3.30.0GHSA-r275-fr43-pm7q

simple-git has blockUnsafeOperationsPlugin bypass via case-insensitive protocol.allow config key enables RCE

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

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

high@modelcontextprotocol/sdk@1.25.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

highsimple-git@3.30.0GHSA-hffm-xvc3-vprc

simple-git is vulnerable to Remote Code Execution

highsimple-git@3.30.0GHSA-jcxm-m3jx-f287

simple-git Affected by Command Execution via Option-Parsing Bypass

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.
configKGMCP_PORT
configKGMCP_STORAGE_PATH
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployKGMCP_PG_CONNECTION_STRING
// 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

16/16 tools missing one or more hints — list_context_roots (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_contexts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_context_tree (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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

12/16 tools referenced in tests (75%)

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

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

1 critical, 3 high severity in production deps — simple-git@3.30.0 (critical), @modelcontextprotocol/sdk@1.25.2 (high)

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.

Dependency freshness

1/11 production deps stale: gray-matter@2023-07-12 (3.1y)

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/teamstove/organized-context-datastore-mcp?variant=verified)](https://m8ven.ai/mcp/teamstove/organized-context-datastore-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 72d776150c265ebe1c8863a435e3433355db2bf8
code hash: 8c5a9a13f5c3923aeb3a6840e35cdedc62daa027a9de8dfac1ee33b3bb3965f2
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