Skip to main content
Glama
mariusei

Scantool - File Scanner MCP

by mariusei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Scantool - File Scanner MCP

No user-submitted related servers found.

    Related Servers

    • MCP Codebase Symbols Server

      klimadev
      A
      license
      A
      quality
      D
      maintenance
      Analyzes codebases and extracts all symbols (functions, classes, methods, interfaces, etc.) from 10+ programming languages into LLM-optimized markdown format. Enables AI assistants to understand entire project structures efficiently without processing full source code.
      2
      5 npm
      MIT

    • XRAY MCP

      srijanshukla18
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to understand and navigate codebases through structural analysis. Provides code mapping, symbol search, and impact analysis using ast-grep for accurate parsing of Python, JavaScript, TypeScript, and Go projects.
      4
      52
      MIT

    • smart-explore

      VasyaYovbak
      F
      license
      A
      quality
      C
      maintenance
      Enables token-efficient structural code exploration using tree-sitter AST parsing, with tools for symbol search, outlines, source unfolding, call graphs, and related-file discovery.
      1
      -

    • mcp-codebase-intelligence

      g-tiwari
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.
      11 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 13 tools

    Disambiguation2/5

    The scan/list/preview family (preview_directory, list_directories, scan_file_content, scan_file, scan_directory) shares nearly identical descriptions and differs only by subtle input-target or output-level details, making tool selection ambiguous. The remaining tools are more distinct, but the overlap among the scanning tools creates real boundary confusion.

    Naming Consistency2/5

    Names mix verb_noun forms (scan_file, search_structures) with bare nouns (surface, overlap, callers, history) and a lone verb (resolve). The scan_* prefix is consistent, but the broader set lacks a single predictable convention, and list_directories vs scan_directory adds further inconsistency.

    Tool Count4/5

    13 tools is a substantial but reasonable surface for a comprehensive code-analysis server, covering scanning, diffing, search, callers, history, and ref resolution. The count is slightly inflated by five overlapping list/scan/preview tools, but overall it remains within a well-scoped range.

    Completeness4/5

    The tool set covers orientation, scanning, search, diffing, branch overlap, callers, history, and symbol resolution, providing broad read-only code-analysis coverage. Minor gaps exist—such as raw full-file content retrieval and explicit definition lookup—but these are workable through existing skeleton and context tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources