Bragproof

← Reports

lsp-mcp-server

Starts with no setup1.1.27npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing

29tools listed
0hosts contacted
0files written
0.2 sto start
98dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y lsp-mcp-server@1.1.27

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.

lsp_server_statusReturned a result under 0.1 s · 19 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

lsp_goto_definition file_path, line, column
Find where a function, class, or variable is defined. More accurate than grep—handles aliases, re-exports, and overloads correctly. Returns file path, line, and column of the definition.
lsp_goto_type_definition file_path, line, column
Find the type that defines a variable, parameter, or return value. Use when you have a variable and want to see its interface/class definition, not where the variable itself is declared.
lsp_find_references file_path, line, column, include_declaration, limit, offset
Find every usage of a symbol across the codebase. Use before renaming or deleting to understand impact. More complete than grep—finds semantic matches, not just text.
lsp_find_implementations file_path, line, column, limit
Find all concrete implementations of an interface, abstract class, or abstract method. Use to understand how an abstraction is actually used in practice.
lsp_hover file_path, line, column
Get the type signature and documentation for any symbol. Use to understand what a function accepts/returns or what type a variable has, without reading its implementation.
24 more tools
lsp_signature_help file_path, line, column
Get parameter hints for a function call. Use when you need to know what arguments a function expects and their types, especially for overloaded functions.
lsp_document_symbols file_path
Get a structured outline of a file: all functions, classes, interfaces, and variables with their types and relationships. Faster and more accurate than reading and parsing the file yourself.
lsp_workspace_symbols query, kinds, limit
Find any function, class, interface, or type by name—no file path needed. Start here when exploring a codebase or locating where something is defined. Supports fuzzy matching.
lsp_file_exports file_path, include_signatures
Get the public API surface of a file: top-level functions, classes, interfaces, and variables with their type signatures. Use to understand what a module exposes without reading the entire file.
lsp_file_imports file_path
Get all imports/dependencies of a file. Shows what modules this file depends on, including ES modules, CommonJS require(), and dynamic imports. Use to understand file dependencies.
lsp_related_files file_path, relationship
Find files connected to a given file: what it imports and what imports it. Use to understand a file's dependencies and dependents before refactoring.
lsp_diagnostics file_path, severity_filter
Get compiler errors, warnings, and hints for a file. Use after making changes to check for type errors, missing imports, or other issues. Diagnostics come from the language server, published or, for servers such as TypeScript 7, requested.
lsp_workspace_diagnostics severity_filter, limit, group_by
Get all errors and warnings across the entire project—no file path needed. Use during initial analysis to find problems or after changes to check overall project health. Only includes files opened in this session.
lsp_completions file_path, line, column, limit
Get intelligent code completion suggestions at a position. Returns available methods, properties, variables, and types that are valid in that context. More accurate than text-based completion.
lsp_rename file_path, line, column, new_name, dry_run
Rename a symbol across the entire codebase safely. Handles all references, imports, and re-exports. Use dry_run=true (default) to preview changes before applying. More reliable than find-and-replace.
lsp_code_actions file_path, start_line, start_column, end_line, end_column, kinds, apply, action_index
Get quick fixes and refactoring suggestions at a position. Use to auto-fix errors, organize imports, extract functions, or apply other automated transformations. Set apply=true to execute an action.
lsp_call_hierarchy file_path, line, column, direction
Trace function calls: who calls this function (incoming) and what it calls (outgoing). Essential for understanding code flow and assessing impact before modifying a function.
lsp_type_hierarchy file_path, line, column, direction
Explore inheritance: find parent classes/interfaces (supertypes) and child classes/implementations (subtypes). Use to understand class relationships before modifying a base class or interface.
lsp_format_document file_path, tab_size, insert_spaces, apply
Format a file according to project style settings (prettier, eslint, etc.). Use after making edits to ensure consistent formatting. Set apply=true to write changes.
lsp_smart_search file_path, line, column, include, references_limit
Get comprehensive information about a symbol in one call: type signature, definition location, all references, implementations, and call hierarchy. Use when you need full context about something instead of making multiple separate queries.
lsp_find_symbol name, kind, include, references_limit
Find a symbol by name alone—no file path or position needed. Returns the definition location plus full context (type info, references, call hierarchy). Use when you know a symbol name but not where it is defined.
lsp_server_status server_id
Check which language servers are running and their state. Use to verify LSP is available before analysis or to debug connection issues.
lsp_start_server server_id, workspace_root
Start a language server manually for a workspace. Usually not needed—servers auto-start when you use other LSP tools. Use only when you need explicit control over server lifecycle.
lsp_stop_server server_id, workspace_root
Stop a running language server to free resources. Servers auto-stop after idle timeout, so manual stop is rarely needed.
lsp_document_highlights file_path, line, column
Find all occurrences of the symbol at a position within the same file, classified as text/read/write. Faster and more local than lsp_find_references when you only care about one file (e.g., quick local rename preview or read-vs-write analysis).
lsp_inlay_hints file_path, start_line, start_column, end_line, end_column, limit
Get inferred type annotations and parameter-name hints for a range of code. Reveals variable types, return types, and named-parameter mappings without one hover per identifier. Ideal for understanding heavily inferred code (TypeScript const/let, Rust let, etc.) at scale.
lsp_selection_range file_path, line, column
Get the chain of semantic ranges enclosing a position — the expression, then its statement, then its block, up to the file. Use to pick the right range for lsp_code_actions (e.g., "extract this expression vs the whole statement").
lsp_folding_ranges file_path, kind_filter
Get the foldable regions of a file (functions, classes, blocks, imports, comments). Use as a quick structural overview before reading specific sections.
lsp_index_files files
Open a batch of files so language servers begin publishing diagnostics for them. Required warm-up before lsp_workspace_diagnostics (which only sees opened files) and before lsp_related_files imported_by. Use a small targeted set rather than the whole workspace.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=18.0.0
Sourcegithub.com/ProfessioneIT/lsp-mcp-server
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-GW/2/DJ3RfGG9FzwRJzXF5RQR2tWMXdEOr3VuBJZKm2x+q3TXTyhOrpjsiN+xbFukwRGrGlaL4W6q6Wa1+EQCA==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/lsp-mcp-server.svg)](https://bragproof.smaverk.com/r/lsp-mcp-server)

New version out? Ask for a fresh report.