check_safe_to_delete

MCP tool from Symbolpeek MCP by pioner92

"Are these files safe to delete?" — one path or a whole set; references within the set don't block

How to use it

Project documentation lists check_safe_to_delete for the Symbolpeek MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.

Install Symbolpeek MCP

$claude mcp add --transport stdio --scope user symbolpeek -- "$HOME/.local/share/symbolpeek/symbolpeek"
FULL SYMBOLPEEK MCP LISTING

Other tools in Symbolpeek MCP (16)

find_calls

"Who calls this symbol (callers) / what does it call (callees)?"

find_dependencies

"Which local symbols does this symbol depend on?"

find_implementations

"Which classes implement this interface or contract?"

find_references

"Where is this symbol referenced across the project?"

get_call_hierarchy

"What callers and callees surround this symbol?"

get_capabilities

"Which operations does each language support?"

get_diagnostics

"What TypeScript compiler diagnostics affect this file or symbol?"

get_document_outline

"What is the nested declaration structure of this file?"

get_type

"What is the inferred type or signature at this location?"

go_to_definition

"Where is the definition behind this usage?"

list_symbols

"What are the top-level symbols in this file?"

read_symbol

"Show me the exact source for this symbol."

read_symbol_context

"Give me this symbol plus its minimal local context."

read_symbols

"Read several symbols at once (batch, cross-file, per-item ok)."

rename_symbol

"Rename this symbol project-wide." Writes files directly — refused before any write if the new name collides with a declaration already in scope

search_symbols

"Where is this symbol defined across the workspace?"