T
tubban1/vibe-monitor
A local architecture advisor for AI coding workflows.
★ 6·updated 2026-11-15
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 6 ★ · tubban1/vibe-monitor · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 6 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
tubban1/vibe-monitor;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Vibe Monitor
Excerpted from the repository README (abridged)
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
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/tubban1-vibe-monitor/)
- Source
- awesome · https://github.com/tubban1/vibe-monitor
- Browse by field
- MCP servers
- Traction
- 6 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.