Skip to main content
Glama
srinivasan-sundaresan95

Orihime

by srinivasan-sundaresan95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Orihime

No user-submitted related servers found.

    Related Servers

    • codebase-memory-mcp

      DeusData
      A
      license
      A
      quality
      A
      maintenance
      High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 159 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.
      15
      43,043
      MIT

    • trace-mcp

      nikolai-vysotskyi
      A
      license
      A
      quality
      A
      maintenance
      Framework-aware code intelligence MCP server that builds a cross-language dependency graph from source code. 53 integrations (Laravel, Django, Rails, Spring, NestJS, Next.js, and more) across 68 languages. 100+ tools for navigation, impact analysis, refactoring, security scanning, session memory, and CI/PR reports — up to 97% token reduction.
      29
      2,674 npm
      175
      MIT

    • code-graph-mcp

      sdsrss
      A
      license
      Not graded
      quality
      A
      maintenance
      A high-performance code knowledge graph server implementing MCP, indexing codebases into a structured AST knowledge graph with semantic search, call graph traversal, and HTTP route tracing.
      3,510 npm
      75
      MIT

    • Graph X

      vugarfamiloglu
      A
      license
      Not graded
      quality
      C
      maintenance
      A knowledge graph MCP server that indexes your codebase into a local SQLite graph and provides tools for project mapping, file summaries, and impact analysis, drastically reducing token usage in AI coding assistants.
      MIT

    • contextshrinker

      bauhaus28
      A
      license
      Not graded
      quality
      C
      maintenance
      Zero-dependency Go MCP server that indexes codebases into an embedded Kùzu graph DB—enabling 90%+ token reduction, precise call-chain queries, and AI architectural health audits.
      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

    A3.8/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is notable overlap in the taint analysis family (find_taint_sinks, find_taint_flows, find_taint_paths, find_reachable_sinks, find_cross_service_taint, find_second_order_injection) and call graph queries (find_callers, blast_radius, find_endpoint_callers). Detailed descriptions help distinguish them, but an agent could misselect between similar-sounding tools.

    Naming Consistency4/5

    Naming follows a mostly consistent verb_noun pattern with find_* for queries and list_* for enumerations. However, there are deviations like search_symbol, get_file_location, ingest_perf_results, index_repo_tool, generate_security_report, estimate_capacity, and blast_radius, which mix conventions. Still readable and predictable overall.

    Tool Count3/5

    33 tools is above the typical heavy threshold (25+), but the server is a comprehensive static analysis platform covering indexing, security, performance, dependencies, and call graphs. While each tool has a purpose, the count feels large and could be consolidated (e.g., merging some taint variants), making it borderline appropriate.

    Completeness4/5

    The toolset covers the core lifecycle of static analysis: indexing, searching, security (taint, license), performance (hotspots, capacity, cascade), dependencies, and call graph traversal. Minor gaps exist, such as no tool to delete a repository or retrieve all methods in a class, but these are not critical to the primary workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources