21 tools from the Vibe Hnindex MCP Server, categorised by risk level.
View the Vibe Hnindex policy →codebase_overview Get a high-level overview of an indexed project: directory structure, language breakdown, entry points, detected frameworks, and key exports. Usefu... 2/5 file_summary Get a detailed summary of a specific file: purpose, exports, imports, files that depend on it, and complexity. More efficient than reading the full... get_dependencies List all imports/dependencies of a specific file. Shows what this file depends on. get_dependents List all files that import/depend on a specific file. Shows what would be affected if this file changes. 2/5 get_file_info Get information about a specific indexed file including its chunks, line ranges, and language. impact_analysis Analyze the transitive impact of changing a file. Uses BFS to find all direct and indirect dependents up to a configurable depth. Essential before ... index_codebase Index an entire codebase directory for later search. Scans all supported source files, chunks them, and stores in the knowledge base with keyword a... 2/5 index_file Index or re-index a single file in an existing project. The project must have been indexed with index_codebase first. list_projects List all indexed projects with their metadata including file count, chunk count, and last indexed time. onboarding_prompt Single markdown blob for agent onboarding: cached project briefing, stats, and optional recent git activity. Output is truncated to max_chars. project_briefing Rule-based project briefing from README, CLAUDE.md, package.json, and indexed stats (no LLM). Results are cached in SQLite until the index fingerpr... project_stats Get detailed statistics about an indexed project: language breakdown, file/chunk counts, total lines, and averages. Useful for understanding codeba... recent_changes Show recent git commits for a project with changed files cross-referenced against the index. Requires git. search Search the indexed codebase. Returns matching code chunks with file paths, line numbers, and relevance scores. Modes: keyword (FTS5), semantic (vec... 2/5 server_diagnostics Health check: Ollama, Qdrant, embedding probe, and config summary. Optionally pass project_name to compare SQLite chunk count with Qdrant point count. smart_context Get comprehensive context for a file or query in a single call: file content preview, imports, dependents, exports, recent git history, and optiona... 2/5 symbol_lookup Find symbol definitions (classes, functions, interfaces, methods) by name in the indexed symbol table. Faster than full-text search for exact ident... unwatch_project Stop watching a project for file changes. watch_project Start watching an indexed project for file changes. When a source file is saved, it will be automatically re-indexed. Uses debouncing to avoid exce... The Vibe Hnindex MCP server exposes 21 tools across 3 categories: Read, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Vibe Hnindex server.
Vibe Hnindex tools are categorised as Read (19), Destructive (1), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept