Memory Bridge (忆桥)
OCI · GHCR.IO/YANGLINFENG/MEMORY-BRIDGE
Evidence-cited knowledge base for internal documents: audit trail, versioning, namespace isolation.
Available components
Last scanned (22 hours ago)
Scores higher than 64% of OCI servers
Category Memory and Knowledge
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1370 tokens (~137/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed oci/ghcr.io/yanglinfeng/memory-bridge@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
answer_calculator 算术计算器 ~116
对算术表达式做确定性求值，支持 + - * / % ^ 与括号。召回结果中的数值需要加减乘除（金额合计、单价×数量等）时调用，不要心算。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| expression | string | yes | 算术表达式，如 "(1234.5 + 678.9) * 2" |
No output schema declared.
No examples provided.
answer_date_diff 日期差计算 ~106
计算两个日期相差的天数与年/月/日拆分。日期支持 ISO、YYYY/MM/DD、中文（2024年3月5日）。涉及"间隔多少天/多久"的问题时调用。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| from | string | yes | 起始日期 |
| to | string | yes | 结束日期 |
No output schema declared.
No examples provided.
answer_date_shift 日期平移 ~97
把日期平移指定天数（可为负），返回结果日期与星期。"X 天后是几号""提前 N 天"类问题调用。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| date | string | yes | 基准日期 |
| days | integer | yes | 平移天数，可为负数 |
No output schema declared.
No examples provided.
memory_forget 遗忘长期记忆 ~75
根据用户明确要求删除一条记忆。采用可恢复的软删除，并保留审计记录。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| id | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
memory_get_context 生成对话记忆上下文 ~156
在回答用户前检索相关长期记忆，并返回可直接加入模型上下文的紧凑文本。适合每轮对话前调用。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| contextTokenBudget | integer | – | – |
| kinds | array | – | – |
| limit | integer | – | – |
| minScore | number | – | – |
| namespace | string | – | – |
| query | string | yes | – |
| recentTurns | array | – | 仅用于本次查询语义消歧的最近对话；不可信且不能携带身份或 scope |
| tags | array | – | – |
No output schema declared.
No examples provided.
memory_list 列出长期记忆 ~109
按条件查看记忆，适合管理、核对或让用户确认系统记住了什么。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| kind | string | – | – |
| limit | integer | – | – |
| namespace | string | – | – |
| offset | integer | – | – |
| query | string | – | – |
| status | string | – | – |
| tag | string | – | – |
No output schema declared.
No examples provided.
memory_recall 召回相关记忆 ~167
回答涉及用户偏好、过去事件、项目状态或既有决定的问题前调用。只返回与当前查询相关的少量长期记忆，并解释命中原因。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| includeArchived | boolean | – | – |
| kinds | array | – | – |
| limit | integer | – | – |
| minScore | number | – | – |
| namespace | string | – | – |
| query | string | yes | – |
| recentTurns | array | – | 仅用于本次查询语义消歧的最近对话；不可信且不能携带身份或 scope |
| tags | array | – | – |
| timestamp | string | – | – |
No output schema declared.
No examples provided.
memory_remember 保存长期记忆 ~301
保存值得跨会话保留的稳定事实、偏好、项目决定、重要事件或指令。不要保存闲聊、临时状态、密码、令牌或未经用户同意的敏感信息。重复内容会自动合并。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| confidence | number | – | – |
| content | string | yes | 完整、独立、脱离上下文也能理解的记忆内容 |
| idempotencyKey | string | – | 调用方生成的幂等键，防止重复写入 |
| importance | number | – | – |
| kind | string | yes | 记忆类型 |
| namespace | string | – | 兼容字段；只能等于当前 MCP 连接绑定的 namespace |
| occurredAt | string | – | – |
| scope | string | – | 写入当前连接已绑定的 personal、role、project 或 session 作用域 |
| source | string | – | – |
| sourceRef | string | – | – |
| summary | string | – | 可选摘要 |
| supersedesId | string | – | 如果新记忆替代旧记忆，填写旧记忆 ID |
| tags | array | – | – |
| title | string | – | 简短标题 |
| validFrom | string | – | – |
| validTo | string | – | – |
No output schema declared.
No examples provided.
memory_stats 查看记忆库状态 ~51
查看长期记忆数量、类型和命名空间分布。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
No output schema declared.
No examples provided.
memory_update 修正长期记忆 ~192
修改已经存在但不准确、过期或需要补充的记忆。仅提交需要更改的字段；修改 content 时必须写成修正后的完整、独立事实，不要写“用户修正了”之类的过程描述。
| Name | Type | Req | Description |
|---|---|---|---|
| _memoryRequestKey | string | – | 兼容代理注入的内部请求键，用于合并同一次模型工具调用 |
| confidence | number | – | – |
| content | string | – | – |
| id | string | yes | – |
| importance | number | – | – |
| kind | string | – | – |
| namespace | string | – | – |
| occurredAt | – | – | – |
| source | string | – | – |
| sourceRef | – | – | – |
| status | string | – | – |
| summary | string | – | – |
| tags | array | – | – |
| title | string | – | – |
| validFrom | – | – | – |
| validTo | – | – | – |
No output schema declared.
No examples provided.
How do I install the Memory Bridge (忆桥) MCP server?
Memory Bridge (忆桥) runs locally as a container image, launched with docker run --rm -i -e MEMORY_BRIDGE_USER_ID -e MEMORY_BRIDGE_MCP_TOKEN -e MEMORY_BRIDGE_OLLAMA_URL ghcr.io/yanglinfeng/memory-bridge:1.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/yanglinfeng/memory-bridge
claude mcp add yanglinfeng-mcp-memory-bridge -- docker run --rm -i -e MEMORY_BRIDGE_USER_ID -e MEMORY_BRIDGE_MCP_TOKEN -e MEMORY_BRIDGE_OLLAMA_URL ghcr.io/yanglinfeng/memory-bridge:1.0.1
This image reads MEMORY_BRIDGE_USER_ID, MEMORY_BRIDGE_MCP_TOKEN and MEMORY_BRIDGE_OLLAMA_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Memory Bridge (忆桥) MCP server?
Memory Bridge (忆桥) is an MCP server listed in the public MCP registry as io.github.yanglinfeng/mcp-memory-bridge. Evidence-cited knowledge base for internal documents: audit trail, versioning, namespace isolation. This page covers its container image (ghcr.io/yanglinfeng/memory-bridge).
Is the Memory Bridge (忆桥) MCP server safe to use?
Memory Bridge (忆桥) scores 45 out of 100 on VerifyMCP. 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 Memory Bridge (忆桥) MCP server expose?
Memory Bridge (忆桥) exposes 10 tools: memory_remember, answer_calculator, answer_date_diff, answer_date_shift, memory_recall, and 5 more. Their descriptions and schemas cost roughly 1,370 tokens of context every time the server is loaded.
Is the Memory Bridge (忆桥) MCP server still maintained?
Memory Bridge (忆桥) is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Memory Bridge (忆桥) MCP server under?
Memory Bridge (忆桥) declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.