Architecture Drift MCP
Compare evidence-linked documentation claims with facts observed in the current source tree.
README
Architecture Drift MCP
Compare evidence-linked documentation claims with facts observed in the current source tree. The server keeps extraction, deterministic comparison, model adjudication, and patch proposals separate so an uncited guess cannot become confirmed architecture drift.
flowchart LR
A[Discover bounded sources] --> B[Cited documentation claims]
A --> C[Cited implementation facts]
B --> D[Deterministic comparison]
C --> D
D --> E{Evidence strength}
E --> F[Aligned]
E --> G[Suspected or unknown]
E --> H[Evidence-bound adjudication]
H --> I[Review-only patch proposal]
Highlights
- Bounded inventory of documentation, manifests, configuration, specifications, and source files
- Deterministic command, environment, endpoint, dependency, and service extraction
- Host-model claim extraction with exact path and line-range validation
- Fresh source hashes that reject mixed old/new citations
- Exact semantic alignment plus conservative
suspectedandunknownstates - Confirmed model adjudication restricted to known claim and fact IDs
- Review-only documentation replacements that never write into the audited project
- Redacted Markdown and JSON reports outside the project tree
Install
uv tool install "git+https://github.com/efficjump/architecture-drift-mcp.git"
architecture-drift-mcp --transport stdio
For source development:
git clone https://github.com/efficjump/architecture-drift-mcp.git
cd architecture-drift-mcp
uv sync --all-extras --locked
uv run architecture-drift-mcp --transport stdio
Generic MCP client configuration
{
"mcpServers": {
"architecture-drift": {
"command": "architecture-drift-mcp",
"args": ["--transport", "stdio"]
}
}
}
The installed command keeps local checkout paths out of client configuration.
Tool workflow
| Stage | Tools |
|---|---|
| Audit state | create_audit, list_audits, get_audit |
| Discovery | discover_sources |
| Evidence | extract_claims, extract_facts |
| Decision | compare_drift, adjudicate_drift |
| Output | propose_doc_patches, build_drift_report |
Deterministic absence never becomes confirmed drift. A confirmed adjudication requires known
implementation fact IDs, while unsupported extractor coverage remains unknown.
Safety model
- Project roots must remain inside
ARCH_DRIFT_ALLOWED_ROOTS. - Symlinks, binary files, and over-limit sources are excluded from extraction.
- Sources are hash-checked again before citation or fact extraction.
- Sampled content is redacted and every returned citation is validated against source lines.
- Patch proposals are persisted externally and never applied by this server.
The path boundary is not an operating-system sandbox. Audit untrusted projects in isolation.
Streamable HTTP
architecture-drift-mcp --transport streamable-http --host 127.0.0.1 --port 8768
The default endpoint is http://127.0.0.1:8768/mcp.
Development
uv sync --all-extras --locked
uv run ruff format --check .
uv run ruff check .
uv run mypy src
uv run pytest --cov --cov-report=term-missing
uv build
See architecture, security policy, and contribution guide.
License
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。