Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MPM-Coding

MCPB · MPM-CODING-V2.11.0.MCPB

Tool-first MCP: AST nav, impact/flow, task chains, memo/recall.

0 this week 50 Trust /100

Last scanned (8 hours ago)

Scores higher than 81% of MCPB servers

Category Developer Tools

Trust breakdown (7 categories)

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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency35
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3582 tokens (~275/item across 13 items; 13 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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.

Changelog

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 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 0
    • Provenance: unverified → fail ▼ security
  • 20 Oct 26 +1
    • Provenance: fail → unverified ▼ security
  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 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.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Analysed mcpb/https://github.com/halflifezyf2680/MPM-Coding/releases/download/v2.11.0/mpm-coding-v2.11.0.mcpb@2.11.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 13 exposed · ~3,582 tokens

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 →

Tool Tokens
check_update ~67

check_update - 检查 MPM-Coding 新版本 用途: 检查 GitHub Releases 是否有新版本, 提示用户手动更新。 参数: 无 触发词: "mpm 更新", "mpm update", "mpm check update"

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

code_impact ~261

code_impact - 改动风险报警 用途: 基于静态索引提示明显上游/下游风险点;用于改前优先检查,不是完整影响范围证明 参数: symbol_name (必填) 要分析的符号名(函数名或类名) 注意:必须是精确的代码符号,不支持字符串搜索 direction (默认: backward) - backward: 谁调用了我(影响上游) - forward: 我调用了谁(影响下游) - both: 双向分析 返回: - 风险等级(low/medium/high) - 明显风险点列表(前10个) - 间接风险线索数量 - 改前优先检查锚点 示例: code_impact(symbol_name="Login", direction="backward") -> 分析谁在调用 Login 函数 触发词: "mpm 影响", "mpm 依赖", "mpm impact"

NameTypeReqDescription
directionstringyes分析方向
symbol_namestringyes要分析的符号名 (函数名或类名)

No output schema declared.

No examples provided.

code_search ~234

code_search - 代码符号定位 (比 grep 更懂代码) 用途: 【精确定位】当你只知道名字(函数名/类名),但不知道它在哪个文件时,别用 grep,用我。 参数速查: query (必填) 符号名,如 "SessionManager"、"handleRequest" scope (可选) 限定目录,如 "internal/core" search_type (可选) any|function|class(默认 any) ⚠️ 注意:query 是符号名,不要写自然语言。 调用示例: { "query": "SessionManager" } { "query": "handleRequest", "scope": "internal/services", "search_type": "function" } 触发词: "mpm 搜索", "mpm 定位", "mpm 符号", "mpm find"

NameTypeReqDescription
querystringyes搜索关键词
scopestringyes限定范围
search_typestringyes符号类型过滤

No output schema declared.

No examples provided.

ensure_languages ~116

ensure_languages - 确保 tree-sitter grammar 已下载 用途: 扫描项目文件扩展名,下载缺失的 tree-sitter grammar。通常在 initialize_project 时自动执行。 参数: project_root (可选) 指定项目根路径。留空时使用当前会话项目。 触发词: "mpm 下载语法", "mpm ensure languages"

NameTypeReqDescription
project_rootstringyes可选项目根路径,留空时使用当前会话项目

No output schema declared.

No examples provided.

flow_trace ~272

flow_trace - 业务流程追踪(文件/函数) 用途: 给 LLM 建立代码阅读候选主链: 先定位入口锚点, 再看上下游候选依赖, 按关键节点顺序阅读源码。 参数: symbol_name 函数名、类名或文件路径, 系统自动识别 scope 限定目录(大项目建议填), 例如 "internal/services" direction both|forward|backward(默认 both) mode brief|standard|deep(默认 brief) max_nodes 输出节点上限(默认 40) 触发词: "mpm 流程", "mpm flow"

NameTypeReqDescription
directionstringyes追踪方向
max_nodesintegeryes输出节点上限
modestringyes输出层级
scopestringyes项目内相对目录路径,例如 internal/services。留空表示整个项目
symbol_namestringyes函数名、类名或文件路径。支持以下格式:函数名如 handleRequest;文件路径如 internal/tools/analysis.go;路径+函数如 internal/tools/analysis.go:handleRequest。系统自动识别类型

No output schema declared.

No examples provided.

index_status ~149

index_status - 查看 AST 索引后台任务状态 用途: 查询 initialize_project 启动的后台索引任务进度、心跳和数据库文件大小。 参数: project_root (可选) 指定项目根路径。留空时使用当前会话项目。 返回: - status/mode/started_at/finished_at - heartbeat(processed/total) - symbols.db / symbols.db-wal / symbols.db-shm 文件大小 触发词: "mpm 索引状态", "mpm index status"

NameTypeReqDescription
project_rootstringyes可选项目根路径,留空时使用当前会话项目

No output schema declared.

No examples provided.

initialize_project ~396

initialize_project - 初始化项目环境与数据库 用途: 任何其他 MPM 操作前,必须先调用此工具初始化项目环境。它会建立数据库索引、检测技术栈并生成项目规则。 参数: project_root (必填) 项目根目录的绝对路径。如果留空,工具会尝试自动探测。 force_full_index (可选) 强制全量索引(禁用大仓库 bootstrap 策略)。默认 false。 skip_rules (可选) 跳过 AGENTS.md 协议注入。默认 false。 说明: - 手动指定 project_root 时必须使用绝对路径。 - 调用前先检查你的上下文/系统提示词中是否已包含 MPM 协议(如用户级 AGENTS.md 已有 MPM 工具协议)。若已包含,传 skip_rules=true 避免项目级 重复注入;若未包含,协议将注入项目根 AGENTS.md 顶部(marker 区段, 幂等更新),客户端自动加载。 示例: initialize_project(project_root="D:/AI_Project/MyProject") -> 初始化指定路径的项目 initialize_project(project_root="D:/AI_Project/MyProject", skip_rules=true) -> 上下文已有 MPM 协议,跳过项目级注入 触发词: "mpm 初始化", "mpm init"

NameTypeReqDescription
force_full_indexboolean–强制全量索引(禁用大仓库bootstrap策略,默认false)
project_rootstring–项目根路径 (绝对路径,留空自动探测)
skip_rulesboolean–跳过AGENTS.md协议注入(上下文已有MPM协议时使用,默认false)

No output schema declared.

No examples provided.

memo ~550

memo - 项目的"黑匣子" (如果不记,等于没做) 用途: 【修改后必选】任何代码/文档修改后,严禁不留记录直接结束。 这不仅是给用户看的,更是为了你自己以后能检索到 "当时为什么这么改"。它是项目演进的唯一真理源 (SSOT)。 参数: items (必填 - JSON 数组): ⚠️ 注意:items 本身就是一个数组,即使只记录一条也要用 [{...}] 包裹 每个数组元素包含以下字段(全部必填): - category: 分类,如 "修改"、"开发"、"决策"、"重构"、"避坑" - entity: 改动的实体(文件名、函数名、模块名) - act: 简要行为描述,如 "修复Bug"、"新增功能"、"技术选型" - path: 文件路径 - content: 详细说明,解释"为什么这么改"而非只说"改了什么" lang (可选,默认 zh): 记录语言,建议始终使用中文 fact_observations (可选): 本次修改揭示的可复用项目经验(每条一句),会追加到项目根 known-facts.md 作 candidate。 只写可复用经验(格式:"在XX条件下应该/不应该YY"),不写任务完成确认或流水账;没有就别填。 完整调用示例(JSON格式): { "items": [ { "category": "修改", "entity": "SessionManager", "act": "修复空指针异常", "path": "core/session.go", "content": "添加 nil 检查,防止未初始化的配置导致 panic" } ], "lang": "zh" } 触发词: "mpm memo", "mpm 记录", "mpm 存档"

NameTypeReqDescription
fact_observationsarray–可选:可复用项目经验(每条一句),追加到项目根 known-facts.md 作 candidate。只写可复用经验(格式:在XX条件下应该/不应该YY),不写任务完成确认或流水账;没有就别填
itemsarrayyes录入事项列表
langstringyes当前用户对话的语言 (zh=中文

No output schema declared.

No examples provided.

open_timeline ~143

open_timeline - 项目演进可视化界面 用途: 生成并展示交互式时间线,可视化项目的开发历史和决策演进。 参数: 无 说明: - 基于 memo 记录生成 project_timeline.html。 - 会尝试自动在默认浏览器中打开生成的文件(Windows 下已加强空格/中文等路径的兼容性,优先使用系统文件关联)。 示例: open_timeline() -> 在浏览器中打开项目演进时间线 触发词: "mpm 时间线", "mpm timeline"

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

persona ~575

persona - AI 人格管理工具 用途: 切换或列出可用的 AI 人格(角色)。通过改变语气、回复风格和思维协议,提升交互体验或特定场景的处理效率。 参数: mode (默认: list) - list: 列出所有可用的预设人格。 - activate: 激活指定的人格。 - create: 新增人格(写入 .mcp-config/personas.json)。 - update: 更新人格(支持重命名)。 - delete: 删除人格。 name (activate/update/delete 模式必填) 目标人格名称或别名。 自然语言触发示例: - "激活人格 孔明" - "切换到白起人格" - "列出所有人格" - "创建人格 xxx" - "删除人格 xxx" create/update 可选字段: - new_name, display_name, hard_directive, aliases - style_must, style_signature, style_taboo, triggers 说明: - 激活人格后,LLM 将严格遵守该角色的语言特征和指令。 - 常驻角色包括诸葛(孔明)、懂王(特朗普)、哆啦(哆啦 A 梦)等。 - 建议在对话中展示简要结果(如已激活人格名称),避免输出冗长内部提示文本。 示例: persona(mode="activate", name="zhuge") -> 切换到孔明人格,使用文言文风格响应 persona(mode="create", name="my_architect", display_name="架构师", hard_directive="回答要简洁严谨") -> 新增自定义人格 触发词: "mpm 人格", "mpm persona", "激活人格", "切换人格", "切换到.*人格", "列出人格", "创建人格", "删除人格"

NameTypeReqDescription
aliasesarrayyes别名列表
avatarstringyes头像或图标
display_namestringyes显示名称
hard_directivestringyes核心指令
modestringyes操作模式
namestringyes人格名称 (activate/update/delete 必填)
new_namestringyes新名称 (update 可选)
style_mustarrayyes必须遵守风格
style_signaturearrayyes标志性表达
style_tabooarrayyes禁用表达
triggersarrayyes触发词

No output schema declared.

No examples provided.

project_map ~191

project_map - 项目导航仪(不知道代码在哪时用) 用途: 宏观视角:当你迷路了,或不知道该改哪个文件时,用我获取项目导航锚点。 参数速查: level symbols|structure(默认 symbols) scope 项目内相对目录(留空=整个项目) ⚠️ 注意:scope 是相对路径,如 "internal/services",不要填绝对路径。 调用示例: { "level": "structure" } { "level": "symbols", "scope": "internal/core" } 触发词: "mpm 地图", "mpm 结构", "mpm map"

NameTypeReqDescription
levelstringyes视图层级
scopestringyes限定范围 (项目内相对目录路径,留空=整个项目)

No output schema declared.

No examples provided.

system_hook ~424

system_hook - 系统钩子 (挂起/列表/释放) 用途: 当任务被阻塞(缺信息/待确认/无法继续)时,用 Hook 挂起当前进度;之后可随时列出/释放并记录结果。 参数: mode (必填): - create: 创建并挂起 Hook - list: 列出 Hook - release: 释放并闭合 Hook create 模式参数: - description (必填) - priority (默认: medium) high/medium/low - task_id (可选) - tag (可选) - expires_in_hours (默认: 0) list 模式参数: - status (默认: open) open/closed release 模式参数: - hook_id (必填) 例如 "#001" - result_summary (可选) 示例: system_hook(mode="create", description="等待用户提供 API 密钥", priority="high") system_hook(mode="list", status="open") system_hook(mode="release", hook_id="#001", result_summary="API 密钥已配置并测试通过") 触发词: "mpm hook", "mpm hooks", "mpm 挂起", "mpm 待办", "mpm 待办列表", "mpm 释放", "mpm 完成"

NameTypeReqDescription
descriptionstringyes待办事项描述 (create)
expires_in_hoursintegeryes过期时间(小时)
hook_idstringyesHook 编号 (release)
modestringyes操作模式
prioritystringyes优先级 (create)
result_summarystringyes完成总结 (release)
statusstringyes状态筛选 (list)
tagstringyes可选标签 (create)
task_idstringyes关联的任务 ID (create)

No output schema declared.

No examples provided.

system_recall ~204

system_recall - 你的记忆回溯器 (少走弯路) 用途: 【下手前推荐】想改某个功能,但不确定以前有没有类似的逻辑?或者怕踩到以前的坑? 用此工具查一下记忆库,避免重复造轮子或重蹈覆辙。 参数策略: keywords (必填) 想查什么就填什么,支持模糊匹配(空格拆分)。 category (可选) 缩小范围:如 "避坑" / "开发" / "决策" 触发词: "mpm 召回", "mpm 历史", "mpm recall"

NameTypeReqDescription
categorystring–过滤类型 (开发/重构/避坑等)
keywordsstringyes检索关键词
limitinteger–返回条数

No output schema declared.

No examples provided.

Install

How do I install the MPM-Coding MCP server?

MPM-Coding ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

mcpb · mpm-coding-v2.11.0.mcpb

Download bundle

The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.

Common questions

What is the MPM-Coding MCP server?

MPM-Coding is an MCP server listed in the public MCP registry as io.github.halflifezyf2680/mpm-coding. Tool-first MCP: AST nav, impact/flow, task chains, memo/recall. This page covers its MCPB bundle (https://github.com/halflifezyf2680/MPM-Coding/releases/download/v2.11.0/mpm-coding-v2.11.0.mcpb).

Is the MPM-Coding MCP server safe to use?

MPM-Coding scores 50 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 MPM-Coding MCP server expose?

MPM-Coding exposes 13 tools: check_update, code_impact, code_search, ensure_languages, flow_trace, and 8 more. Their descriptions and schemas cost roughly 3,582 tokens of context every time the server is loaded.