Skip to main content
Glama
blas0

rev-eng-cursor-regex-mcp

by blas0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to rev-eng-cursor-regex-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Desktop Tools

      andrey-zhuravl
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching text across configured local workspaces using ripgrep. Provides secure text search capabilities within defined workspace boundaries through both MCP server and CLI interfaces.
      MIT

    • File Search MCP

      elad12390
      A
      license
      A
      quality
      D
      maintenance
      Enables blazingly fast file and content searching in large codebases using ripgrep, with intelligent filtering, fuzzy finding, and directory tree visualization while respecting .gitignore and avoiding common bloat directories.
      4
      15 npm
      2
      MIT
    • Cometix Indexer by CometixAI

      Cometix Indexerofficial

      CometixAI
      F
      license
      Not graded
      quality
      D
      maintenance
      A local indexing and retrieval service that enables semantic code search by wrapping Cursor's backend RepositoryService. It provides tools for indexing local workspaces and performing incremental semantic searches with automatic synchronization.
      67
      -
    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

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: index management (ensure, status, clear), search (literal, regex, plan), query explanation (explain), and document inspection (inspect_terms). No functional overlap.

    Naming Consistency5/5

    All tools follow a consistent 'category.action' dot notation (e.g., index.ensure, search.literal), making naming predictable and easy to understand.

    Tool Count5/5

    8 tools is well within the ideal 3-15 range. The count is sufficient to cover the domain without being excessive.

    Completeness4/5

    The tool set covers index lifecycle, two search modes, planning, explanation, and n-gram inspection. A potential gap is the lack of a tool to list indexed files explicitly, but index.status provides similar info. Otherwise, it's well-rounded.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources