HyperMarrow
NPM · @QIANSHITECH/HYPERMARROW-MCP · SCANNED SEP 26
Local-first long-term memory for AI coding agents. Stored on your own machine.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 11 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 473 tokens (~39/item across 12 items; 7 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 86% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the HyperMarrow MCP server?
HyperMarrow runs locally as an npm package, launched with npx -y @qianshitech/hypermarrow-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @qianshitech/hypermarrow-mcp
claude mcp add cool-qianshi-hypermarrow -- npx -y @qianshitech/hypermarrow-mcp
{
"mcpServers": {
"cool-qianshi-hypermarrow": {
"command": "npx",
"args": [
"-y",
"@qianshitech/hypermarrow-mcp"
]
}
}
} {
"servers": {
"cool-qianshi-hypermarrow": {
"command": "npx",
"args": [
"-y",
"@qianshitech/hypermarrow-mcp"
]
}
}
} codex mcp add cool-qianshi-hypermarrow -- npx -y @qianshitech/hypermarrow-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cool-qianshi-hypermarrow": {
"type": "local",
"command": [
"npx",
"-y",
"@qianshitech/hypermarrow-mcp"
],
"enabled": true
}
}
} openclaw mcp add cool-qianshi-hypermarrow --command npx --arg -y --arg @qianshitech/hypermarrow-mcp
mcp_servers:
cool-qianshi-hypermarrow:
command: "npx"
args: ["-y", "@qianshitech/hypermarrow-mcp"] {
"McpServers": {
"cool-qianshi-hypermarrow": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@qianshitech/hypermarrow-mcp"
]
}
}
} assistant mcp add cool-qianshi-hypermarrow -t stdio -c npx -a -y @qianshitech/hypermarrow-mcp
{
"mcpServers": {
"cool-qianshi-hypermarrow": {
"command": "npx",
"args": [
"-y",
"@qianshitech/hypermarrow-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 15 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed npm/@qianshitech/hypermarrow-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
memory_check ~53
决策前查询历史经验和规则建议。做重要决策前调用。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 计划执行的动作 |
| context | object | – | 上下文（task/phase等） |
No output schema declared.
No examples provided.
memory_health ~25
记忆使用率健康自检，返回使用状态和警告建议。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
memory_record ~77
记录决策结果，驱动经验学习。决策执行后调用（outcome: success/failure/partial）。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 执行的动作 |
| context | object | – | 上下文 |
| note | string | – | 备注/教训 |
| outcome | string | yes | 结果 |
No output schema declared.
No examples provided.
memory_search ~67
搜索 HyperMarrow 记忆库（情景记忆+知识图谱）。决策前/不确定时用此工具查历史经验。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 结果数（默认5，最大20） |
| query | string | yes | 搜索关键词 |
No output schema declared.
No examples provided.
memory_store ~59
存档消息到 HyperMarrow 情景记忆。重要对话/工作完成后调用。写入决策引擎会自动识别关键信息。
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | 要存档的消息内容 |
No output schema declared.
No examples provided.
profile_list ~16
列出全部核心记忆。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
profile_set ~56
设置核心记忆（永不遗忘的关键信息，如项目路径、常用工具、用户偏好）。
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | 记忆名称 |
| value | string | yes | 记忆内容 |
No output schema declared.
No examples provided.
What is the HyperMarrow MCP server?
HyperMarrow is an MCP server listed in the public MCP registry as cool.qianshi/hypermarrow. Local-first long-term memory for AI coding agents. Stored on your own machine. This page covers its npm package (@qianshitech/hypermarrow-mcp).
Is the HyperMarrow MCP server safe to use?
HyperMarrow scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HyperMarrow MCP server expose?
HyperMarrow exposes 7 tools: memory_search, memory_store, memory_check, memory_record, profile_set, and 2 more. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.
Is the HyperMarrow MCP server still maintained?
HyperMarrow is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the HyperMarrow MCP server under?
HyperMarrow declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.