MCP Hook Conformance

Name: MCP Hook Conformance
Author: studiomeyer-io

作者：studiomeyer-io版本 0.1.3i★ –i在你的电脑上运行

注册名称io.studiomeyer/hook-conformance

安装

概览

作者提供的说明（英文原文）

Audits MCP servers for Claude Code mcp_tool hook readiness: idempotency, latency, side-effects.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "hook-conformance": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-hook-conformance"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add hook-conformance -- npx -y mcp-hook-conformance

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "hook-conformance": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-hook-conformance"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "hook-conformance": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-hook-conformance"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 studiomeyer.io 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32464 个服务器的 0%
发布到注册中心的时间比此分类中其他 32464 个服务器的 27% 更新
基础检查结果等于或优于此分类中其他 32464 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MCP Hook Conformance 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.3）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, yontu

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

yontu

作者：senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Part of the [StudioMeyer MCP Stack](https://studiomeyer.io) — Built in Mallorca 🌴 · ⭐ if you use it

mcp-hook-conformance

Test-harness CLI that audits any MCP server for Claude Code v2.1.118 mcp_tool lifecycle-hook readiness.

The third foundation pillar:

mcp-protocol-conformance says: does the server speak the protocol?
mcp-server-attestation says: who signed this server?
mcp-hook-conformance says: is it safe to call this tool from a Stop, PreCompact, or UserPromptSubmit hook?

A note from us

We have been building tools and systems for ourselves for the past two years. The fact that this repo is small and has few stars is not because it is new. It is because we only just decided to share what we have built. It is not a fresh experiment, it is a long story with a recent commit.

We love building things and sharing them. We do not love social media tactics, growth hacks, or chasing stars and followers. So this repo is small. The code is real, it gets used, issues get answered. Judge for yourself.

If it helps you, sharing, testing, and feedback help us. If it could be better, an issue is more useful. If you build something with it, tell us at hello@studiomeyer.io. That genuinely makes our day.

From a small studio in Palma de Mallorca.

Install

npm install -g mcp-hook-conformance

Or run without install:

npx mcp-hook-conformance check ./hook-conformance.config.json

Quick start

# 1. Scaffold a config

npx mcp-hook-conformance init --server-name my-mcp-server

2. Edit hook-conformance.config.json (point command/args at your server)

3. Run the audit

npx mcp-hook-conformance check ./hook-conformance.config.json

Exit codes:

0 audit passed (no FAILs)
1 audit produced at least one FAIL
2 config error (missing file, invalid schema, unknown suite name)

Subcommands

Subcommand	Args	Description
`check`	` [--output=human\	json\	junit] [--suite=...] [--tool= ] [--tries= ]`	Run audit; emits report to stdout.
`init`	`[--server-name= ] [--force]`	Write example `hook-conformance.config.json` to cwd.
`explain`		Print full explanation and remediation for a finding (e.g. `IDEMP-001`).
`version-info`	—	Print tool version and supported MCP-spec range. (Alias: `version`.)

This is a CLI, not an MCP server. Do NOT run mcp-hook-conformance via mcp-inspector — the package declares mcp.specVersion for the targets it audits, not because it speaks MCP itself. Inspector will EACCES on dist/index.js (which is the library export) by design.

Audit suites

Suite	What it checks	Weight
`idempotency`	Same input N times produces same output, no UUIDs/timestamps unless annotated.	30
`side-effects`	Read-only tools must not mutate server state. Requires `stateProbe` config.	25
`latency`	p50 < 30s, p95 < 60s (configurable). 5 samples after 1 warmup call.	20
`determinism`	Response shape stable across calls; no float drift.	15
`dsgvo`	Tool description mentions data flow / retention / deletion (whole-word heuristic).	10

Suite scoring: PASS = 100, WARN = 60, INDETERMINATE = 50, FAIL = 0. Tool score = weighted average across configured suites. Aggregate score = mean of tool scores.

Config format

"$schema": "https://studiomeyer-io.github.io/mcp-hook-conformance/config.schema.json", "server": { "name": "my-mcp-server", "transport": "stdio", "command": "npx", "args": ["-y", "my-mcp-server"], "env": {} }, "suites": ["idempotency", "latency", "determinism", "side-effects", "dsgvo"], "tries": 3, "thresholds": { "latencyP50Ms": 30000, "latencyP95Ms": 60000 }, "probes": [ { "name": "search_things", "args": { "query": "audit-fixed-input" }, "stateProbe": { "tool": "list_things", "args": {} } } ], "toolFilter": ["search_things", "get_thing"] }

probes lets you pin specific arguments per tool and (for read-only tools) a stateProbe so the side-effects suite can detect mutations. Without a stateProbe the side-effects suite returns INDETERMINATE for that tool.

Finding codes

Code	Suite	Severity	Title
IDEMP-001	idempotency	FAIL	Tool output diverges across identical calls
IDEMP-002	idempotency	WARN	Response contains timestamps without `nondeterministic` annotation
IDEMP-003	idempotency	WARN	Response contains UUID/random IDs without `nondeterministic` annotation
LAT-001	latency	FAIL	Tool exceeded p95 latency budget
LAT-002	latency	WARN	Tool p50 latency above 30 seconds
DET-001	determinism	FAIL	Floating-point output drift between calls
DET-002	determinism	WARN	Response shape varies between calls
SIDE-001	side-effects	FAIL	Read-only tool produced state delta
SIDE-002	side-effects	INDETERMINATE	No state-probe configured for side-effect detection
DSGVO-001	dsgvo	FAIL	Destructive tool lacks deletion / retention documentation
DSGVO-002	dsgvo	WARN	Tool description missing data-flow keywords

Run mcp-hook-conformance explain for full remediation text.

Compatibility

Component	Version
MCP spec	2025-06-18
Claude Code	>= 2.1.118 (mcp_tool lifecycle hooks)
Node	>= 20.0.0
`@modelcontextprotocol/sdk`	^1.29.0

Tested transports:

stdio (primary)
HTTP streamable (experimental, audit semantics same as stdio)

Reference smoke tests

The tests/smoke/ suite runs the audit against production tenants of mcp-nex and mcp-crm. Opt-in:

RUN_SMOKE_TESTS=1 npm run test:smoke

Snapshot drift triggers a manual review, not a CI fail.

Limitations (read these)

Side-effect detection is not hermetic. Without a stateProbe we cannot black-box prove a read-only tool is pure. We return INDETERMINATE instead of false-positive FAIL.
Latency is end-to-end stdio roundtrip. Includes JSON-RPC framing, not pure compute.
DSGVO suite is keyword heuristic. It catches missing docs reliably; "looks compliant" is not legal advice.
No auto-fix. This tool reports findings; you fix them.

About StudioMeyer

StudioMeyer is an AI and design studio based in Palma de Mallorca, working with clients worldwide. We build custom websites and AI infrastructure for small and medium businesses. Production stack on Claude Agent SDK, MCP and n8n, with Sentry, Langfuse and LangGraph for observability and an in-house guard layer.