Infinite Context Keeper (sujkh85/infinite-context-keeper-node) is an MCP server listed on the M8ven Trust Index. It scores 64 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
64/100

Infinite Context Keeper

MCP server providing context usage estimation, conversation compaction, and durable semantic memory via local embeddings and SQLite.

→ sujkh85/infinite-context-keeper-node· 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

sujkh85

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: 1 critical, 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// 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.

get_server_info

런타임 진단: 패키지·Node 버전, 해석된 data_dir, embedding_enabled, sqlite-vec 활성 여부, 임베딩 파이프라인 로드 여부 등.

get_context_usage

MCP 호스트가 넘기는 used_tokens·대화 본문·tool 결과 문자열을 tiktoken으로 합산해 컨텍스트 사용량을 추정합니다.

trigger_compaction

summarization_start_ratio(기본 75%) 이상일 때만 실행하도록 context_percentage 또는 used_tokens+max_tokens로 검증합니다.

save_memory

시맨틱 메모리에 project_id·session_id 스코프로 저장합니다. 동일 key는 upsert됩니다.

semantic_search_memory

관련 메모리 청크를 반환합니다. sqlite-vec(vec0) KNN이 켜지면 DB 내 벡터 인덱스로 검색하고, 아니면 JS 코사인으로 폴백합니다.

inject_relevant_memories

semantic_search_memory와 동일 스코프로 검색 후 tiktoken 예산 내 마크다운 블록을 만듭니다.

search_and_inject_memory

새 세션/compaction 직후 컨텍스트 상단 주입 블록을 반환합니다.

list_memories

SQLite에 저장된 compaction 요약 등의 메타를 나열합니다.

delete_memory

save_memory로 저장한 semantic_memories 항목을 삭제합니다. id 직접 삭제 또는 (project_id+session_id+key) 기준 삭제를 지원합니다.

project_get_status

Project Brain: 프로젝트 메타, 마일스톤·태스크, 최근 결정/지식, Unity 파일 인덱스 건수를 한 번에 조회합니다. project_id 생략 시 default_project_id.

project_create_milestone

Project Brain: 마일스톤을 추가합니다(자동 order_num).

task_break_down

Project Brain: 마일스톤을 세부 태스크로 나눕니다. tasks가 비어 있으면 마일스톤 정보와 함께 모델이 tasks 배열을 채워 재호출하도록 안내합니다.

task_update

Project Brain: 태스크 상태·노트(설명에 타임스탬프 부가)·누적 actual_hours 갱신.

unity_scan_project

Unity 프로젝트 루트(기본: process.cwd)를 스캔해 project_files 테이블을 갱신합니다. Assets가 있으면 그 하위 위주로 .cs 등 인덱싱.

memory_search

시맨틱 메모리(semantic_memories) + 결정/지식 테이블 텍스트에 로컬 임베딩 코사인 랭킹을 합쳐 검색합니다.

project_resume

새 세션 시작 시 호출: 프로젝트 브레인 요약 마크다운(inject_block) + 구조화 JSON + 최근 compaction 스니펫 + 시맨틱 상위 청크.

reset_entire_database

로컬 infinite_context_keeper.sqlite의 사용자 데이터 전부 삭제(메모·시맨틱·프로젝트 브레인·컴팩션·Unity 인덱스 등). 되돌릴 수 없음. confirm을 정확히 보내야 실행됩니다.

// known CVEs in dependencies1 critical2 high1 low

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

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

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

highjs-yaml@4.1.1GHSA-52cp-r559-cp3m

js-yaml: YAML merge-key chains can force quadratic CPU consumption

highjs-yaml@4.1.1GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

lowjs-yaml@4.1.1GHSA-h67p-54hq-rp68

JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases

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.
configICK_EMBEDDING_ENABLED임베딩 끄기: YAML embedding_enabled: false 또는 =0 이면 시맨틱 전용 도구(save_memory, semantic_search_memory 등)는 비활성 안내 오류를 반환하고, search_and_inject_memory 는 시맨틱 순위 없이 텍스트 청크 위주로 동작하며, 컨텍스트 주입에서 시맨틱 메모 구간은 생략됩니다.
configICK_SETTINGS_YAML2. Point at your own YAML (absolute path) for per-project overrides.
// 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 — get_server_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_context_usage (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); trigger_compaction (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

Only 0/17 tools referenced in tests (0%)

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

Production dependencies are patched

0 critical, 2 high severity in production deps — js-yaml@4.1.1 (high), js-yaml@4.1.1 (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/5 production deps stale: @xenova/transformers@2024-05-29 (2.3y)

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 6 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/sujkh85/infinite-context-keeper-node?variant=verified)](https://m8ven.ai/mcp/sujkh85/infinite-context-keeper-node)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ddb4848ffc34d062900ad0ebff0f4f30058562df
code hash: f123eafb8c9b59bba119cee4a99b41d71d48869775de70b8e2e8f95236be9c25
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