{"id":"mytheclipse-rust-mcp-server","name":"rust-mcp-server","homepage":null,"repo_url":"https://github.com/MythEclipse/rust-mcp-server","category":"ai-ml","subcategories":[],"tags":["mcp","rust","code-analysis","ast","static-analysis","code-navigation","refactoring","json-rpc","stdio"],"what_it_does":"An MCP (Model Context Protocol) server for Rust codebases that exposes tools to parse/check Rust files, index workspaces into analysis graphs, navigate to definitions/references, detect code smells, and provide refactoring suggestions. It communicates via JSON-RPC 2.0 over stdio (e.g., run as a subprocess in MCP clients), with Docker-based deployment described in the README.","use_cases":["AI-assisted navigation of a Rust repository (goto definitions, find references)","Automated static analysis via AST parsing (syntax checks, complexity/size heuristics)","Workspace indexing to build call/type/module graphs for downstream reasoning","Code smell detection (unused/private functions, long/high-complexity functions, large structs/enums)","Refactoring suggestion generation for Rust code review workflows"],"not_for":["Production security scanning or compliance-grade auditing","Running on untrusted or malicious code without sandboxing expectations","Providing exact compiler-verified results for all semantics (it appears heuristic/AST-based, not a full compiler pipeline)","Use cases requiring authenticated multi-tenant access control and network-exposed APIs"],"best_when":"Used locally or in a controlled container environment where an MCP-capable AI coding assistant can spawn the server over stdio and analyze the codebase on-demand.","avoid_when":"Avoid exposing it over the network (it is described as stdio-based) or using it on sensitive code without considering what files are accessible via mounted volumes; avoid assuming it enforces authorization or strong access boundaries since none are described.","alternatives":["Language Server Protocol (LSP) for Rust (e.g., rust-analyzer) with MCP/LSP bridge tooling","tree-sitter-based Rust analysis tools","Static analysis suites like clippy (for some diagnostics) and cargo-audit (for dependency security)","Custom Rust code analysis using syn/quote/tarpaulin in bespoke tooling","Other MCP servers focused on code navigation and repository indexing"],"af_score":68.2,"security_score":43.2,"reliability_score":20.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:23:14.557837+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication mechanism is described. The server is designed for stdio communication (typically local/container subprocess usage)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing is not described in the provided README content (appears to be an open-source style repository with Docker image reference)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":68.2,"security_score":43.2,"reliability_score":20.0,"mcp_server_quality":78.0,"documentation_accuracy":82.0,"error_message_quality":null,"error_message_notes":"Only a single error example is shown; retry/idempotency semantics are not described.","auth_complexity":100.0,"rate_limit_clarity":5.0,"tls_enforcement":100.0,"auth_strength":5.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":80.0,"security_notes":"Transport is described as stdio inside containers (no network API, no TLS discussion needed). No authentication/authorization or scope model is described, so any access control is left entirely to how the process/container is managed. The README does not mention secret management; it only notes RUST_LOG. Dependency hygiene cannot be fully assessed from the provided content.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":0.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":"Idempotency is not explicitly documented. Tools like indexing may be repeatable but behavior, caching, and side effects are not specified.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Communication is via stdio JSON-RPC 2.0; agents must launch it as a subprocess (e.g., via Docker run) rather than calling an HTTP endpoint.","Tools expect absolute paths to files/directories (e.g., check_file uses path, index_workspace uses root); incorrect paths will likely error.","Indexing may be compute-heavy for large workspaces; there is no documented rate/throughput guidance."]}}