Feature: Contract verification panel (pin tool contracts, diff on reconnect)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start by tracing the Inspector’s existing tools, resources, prompts, and reconnect flows, then read the linked PIN-SPEC and reference implementation for hashing and comparison behavior. Identify the UI entry point and existing test locations for connection and inspection features. Done means a connected server can pin canonicalized contract hashes, compare them after reconnect, and display added, removed, and changed tools with the proposed direction grading.
由索引模型根据 Issue 内容生成。
描述
Feature: Contract verification panel (pin tool contracts, diff on reconnect)
Problem
The Inspector shows a server's current tools, resources, and prompts at a point in time. But there is no way to know if the tool contracts changed between sessions. MCP servers can silently add, remove, or modify tool definitions between connections (deploy, version bump, feature flag), and the Inspector has no mechanism to surface this.
We ran a drift watch over 24 popular MCP servers for two months and found 336 silent contract changes, including silent tool removals (Shopify dropped two validators, HubSpot removed a tool with no release notes channel). Full corpus: rugsnare drift-watch.
Proposal
Add a "Contract" tab or panel that:
- Pins the surface on first connect: hash each tool's
{name, description, inputSchema}by canonicalized sha-256 - Compares on reconnect: after a server restart/reconnect, diff the current tools/list against the pinned snapshot
- Surfaces changes: show added / removed / changed tools with direction grading (breaking, loosened, expanded, cosmetic)
This would complement the Inspector's existing inspection capabilities with a temporal dimension: not just "what does this server expose" but "has what it exposes changed since I last looked."
Reference implementation
We ship a standalone CLI that does exactly this (rugsnare, Apache-2.0, zero dependencies). The Inspector could either integrate the hashing/comparison logic directly or shell out to rugsnare as an optional dependency. The pin format is an open spec (PIN-SPEC) with a POLICY class for verifier upgrades and an IDENTITY class for deployment changes.
Use cases
- Developer: connect to a dev server, pin, upgrade the server, reconnect, see what changed before your agent does
- Security reviewer: pin a production server, monitor for contract drift as part of an audit
- CI gate: the same pins can be used in CI to fail builds on breaking contract changes
The OWASP MCP Security Cheat Sheet now recommends pinning tool contracts (PR #2764, merged; cheat sheet), so this aligns with where the ecosystem is heading.
- 主要语言
- TypeScript
- 星标
- 11.1k
- 派生
- 1.6k
- 平均合并
- 5 小时 38 分钟
- 30 天内合并 PR
- 152
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/inspector 的其他 Issue
-
chore v2
难度 2/5 1-3 小时 新手友好度 78/100
modelcontextprotocol/inspector#2752 ·
维护者通常 1 天内回复
-
Release 2.12.0 step 1: bump version to 2.12.0 on v2/main可能已有人在做 @cliffhall 今天认领。 未关闭chore v2
modelcontextprotocol/inspector#2762 · 已指派 1 人 ·
维护者通常 1 天内回复
-
documentation v2
难度 3/5 1-2 天 新手友好度 54/100
modelcontextprotocol/inspector#2755 ·
维护者通常 1 天内回复
-
Static OAuth client loses its SEP-2352 issuer stamp across SDK saves and restarts可能已有人在做 @rajnish-verma-22172 今天认领。 未关闭bug v2
难度 3/5 1-2 天 新手友好度 72/100
modelcontextprotocol/inspector#2751 · 2 条评论 ·
维护者通常 1 天内回复
-
enhancement v2
难度 3/5 1-2 天 新手友好度 67/100
modelcontextprotocol/inspector#2750 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/inspector 的全部 Issue
相似的 Issue
-
agent/scanner help wanted hive/claimed-by-scanner kind/bug stage/020-claimed
难度 2/5 1-3 小时 新手友好度 90/100
hivecommons/rationguard#315 ·
维护者通常 1 天内回复
-
agent-ready area: ui-sdk priority: p3 type: chore
难度 2/5 1-3 小时 新手友好度 76/100
schlessera/brain-kit#2534 ·
维护者通常 1 天内回复
-
bug lane:gh-5
难度 2/5 1-3 小时 新手友好度 72/100
LLM-4-People/bridlewise-testing#122 ·
维护者通常 1 天内回复
-
bug priority: P2
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement priority:low ready-for-dev
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复