T
tubban1/vibe-monitor
A local architecture advisor for AI coding workflows.
★ 6·更新 2026-11-15
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 6 ★ · tubban1/vibe-monitor · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 6 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
tubban1/vibe-monitor;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Vibe Monitor
以下摘录自该仓库的 README(片段)
A local architecture advisor for AI coding workflows. AI agents ship features fast; Vibe Monitor helps you see when architectural complexity is accumulating and what actually needs attention.
## The open-source MCP server
This repository contains an actual local MCP server (stdio transport), not only an npm installer or a cloud dashboard. The MCP server runs on your own computer and exposes read-only architecture checks and change-history snapshots to an MCP-capable coding agent. It does not rewrite your project source.
Example MCP tools implemented in src/mcp.js:
| MCP tool | What it does locally |
| vibe_session_start | Start or resume a bounded assessment of one coding project |
| vibe_project_status | Read the current project's architecture signals without creating a snapshot |
| vibe_checkpoint | Record a post-change snapshot to compare structural evolution |
| vibe_findings | Show prioritized findings and concrete next steps |
| vibe_evolution_audit | Inspect architecture evolution across recorded checkpoints |
| vibe_version | Inspect the actual running/installed version |
Install and register the local MCP server with supported agents:
sh
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install
Direct stdio MCP command (for clients that configure command / args themselves; Node.js 22+):
sh
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest mcp
The npm package implements both the installer and MCP server. The server's official name is io.github.tubban1/vibe-monitor; its registry manifest declares the local mcp argument. Some analysis features depend on the signed Cloud scoring policy; installing does not grant cloud access to your source code. See the telemetry details below.
## Get started — official stable release
The official open-source MCP server and installer are distributed through npm as @vibe-monitor/setup@latest. This source tree targets the reviewed stable package @vibe-monitor/setup@1.0.15. Verify publication with npm view @vibe-monitor/setup dist-tags.latest (a source version alone does not establish npm availability); the previous verified npm release was 1.0.14 (2026-11-03).
bash
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install
On a new install, bounded pseudonymous product telemetry defaults ON, with notice. Use install --no-telemetry or vibe-monitor telemetry off to disable collection; this pauses Free architecture analysis. An existing opt-out survives reinstall. No activation code is required.
Not sure whether your projects need it? Give your coding Agent this one canonical instruction:
Analyze accessible code projects and return a direct recommendation →
The Agent must inspect code projects already accessible in its current workspaces, decide which would benefit (if any), and report the results to you in the chat. No installation or external report submission occurs during the assessment.
## Your source code is not uploaded
## The open-source MCP server
This repository contains an actual local MCP server (stdio transport), not only an npm installer or a cloud dashboard. The MCP server runs on your own computer and exposes read-only architecture checks and change-history snapshots to an MCP-capable coding agent. It does not rewrite your project source.
Example MCP tools implemented in src/mcp.js:
| MCP tool | What it does locally |
| vibe_session_start | Start or resume a bounded assessment of one coding project |
| vibe_project_status | Read the current project's architecture signals without creating a snapshot |
| vibe_checkpoint | Record a post-change snapshot to compare structural evolution |
| vibe_findings | Show prioritized findings and concrete next steps |
| vibe_evolution_audit | Inspect architecture evolution across recorded checkpoints |
| vibe_version | Inspect the actual running/installed version |
Install and register the local MCP server with supported agents:
sh
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install
Direct stdio MCP command (for clients that configure command / args themselves; Node.js 22+):
sh
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest mcp
The npm package implements both the installer and MCP server. The server's official name is io.github.tubban1/vibe-monitor; its registry manifest declares the local mcp argument. Some analysis features depend on the signed Cloud scoring policy; installing does not grant cloud access to your source code. See the telemetry details below.
## Get started — official stable release
The official open-source MCP server and installer are distributed through npm as @vibe-monitor/setup@latest. This source tree targets the reviewed stable package @vibe-monitor/setup@1.0.15. Verify publication with npm view @vibe-monitor/setup dist-tags.latest (a source version alone does not establish npm availability); the previous verified npm release was 1.0.14 (2026-11-03).
bash
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install
On a new install, bounded pseudonymous product telemetry defaults ON, with notice. Use install --no-telemetry or vibe-monitor telemetry off to disable collection; this pauses Free architecture analysis. An existing opt-out survives reinstall. No activation code is required.
Not sure whether your projects need it? Give your coding Agent this one canonical instruction:
Analyze accessible code projects and return a direct recommendation →
The Agent must inspect code projects already accessible in its current workspaces, decide which would benefit (if any), and report the results to you in the chat. No installation or external report submission occurs during the assessment.
## Your source code is not uploaded
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/tubban1-vibe-monitor/)
- 来源
- awesome · https://github.com/tubban1/vibe-monitor
- 按领域浏览
- MCP 服务
- Traction
- 6 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。