Cli
UnclaimedThe Vibgrate CLI scans your codebase for upgrade drift — the gap between the dependency versions you run and the versions you should run. It produces a deterministic Upgrade Drift Score (0–100), a full context-aware dependency graph, and actionable findings enriched with AI-assisted upgrade guidance to help you maintain a healthy, secure codebase.
Set up this server
01 / Choose your client
02 / Before you connect
Authentication is not specified. Check the project instructions before connecting.
Project instructions03 / Add the configuration
claude mcp add --transport stdio 'vibgrate-cli' -- 'npx' '-y' '@playwright/mcp'04 / Check it in your client
Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.
More in Security
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
24 of 24 tools
Documented tools (24)
From project documentation. A server handshake does not verify each tool’s description or behavior.
check_drift
offline dependency inventory with optional git who-added attribution.
compress_content
/ retrieveoriginal / compressionstats (with --compress) — shrink a tool output before it enters the context, expand a marker back to the original or just the slice you need, and report what compression saved.
find_path
shortest connection between two symbols.
get_facts
deterministic facts for a node (contract / invariant / characterization).
get_graph_summary
code map overview: counts, languages, top areas and hubs.
get_node
inspect one symbol: signature, callers, callees, area.
graph_impact
Blast radius of changing a symbol
guide_node
cited standards and practices for a node (OWASP/CWE).
impact_of
blast radius of a change: dependents, files, covering tests, risk.
library_docs
version-correct usage docs for a library, sliced to a token budget.
list_areas
code areas (communities) by size.
list_hubs
most-depended-on symbols.
list_models
local models on disk (Ollama / LM Studio / gguf).
list_vulnerabilities
known vulnerabilities from the last vg scan --vulns: CVE, severity, CVSS, fixed version.
memory_search
/ memorysave (with --memory) — project-scoped memory shared across your AI agents.
orient
start here: project overview, entry points, where to look first.
query_graph
find code by meaning: symptoms, relationships, what-breaks-if.
resolve_library
resolve a library to its canonical id and the version your project uses.
run_command
Run tests, builds, anything else
search_code
Search the code graph — symbols and relations, plus a literal sweep for exact phrases
search_symbols
find a symbol by name or literal string.
tests_for
which tests cover a symbol.
upgrade_impact
what breaks if you upgrade a package: major distance, import blast radius, vulns fixed.
vuln_attribution
who introduced each open vulnerability, exposure windows, CRA remediation metrics.
Tool change history
FAQ
Questions about Cli MCP Server
- How do I connect Cli MCP Server to Claude?
- Run `claude mcp add vibgrate-cli -- npx -y @playwright/mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
- Is Cli MCP Server free?
- The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Cli MCP Server do?
- Cli MCP Server documents 24 tools to the agent, including check_drift, compress_content, find_path. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.