Skip to main content
Glama
Valyay

Nanostores MCP

by Valyay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Nanostores MCP

No user-submitted related servers found.

    Related Servers

    • ast-impact-mapper-mcp

      vola-trebla
      A
      license
      A
      quality
      D
      maintenance
      MCP server that analyzes TypeScript/JavaScript codebases via AST parsing and dependency graph tracing to identify affected tests, detect dead code, circular dependencies, and trace import chains, enabling AI agents to run only relevant tests.
      15
      49
      MIT

    • codetest-mcp

      jihyun0410
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for static code analysis using AST parsing and linters, providing tools to detect syntax errors, type issues, typos, and incorrect variable usage across multiple languages. It supports headless linting with tools like ast_check, lint_check, and health.
      -

    • javascript-mcp-server

      aferreiraguido
      A
      license
      C
      quality
      C
      maintenance
      Deterministic MCP server for semantic analysis of JavaScript/TypeScript codebases, including frameworks like Vue, Angular, React, and Node. It provides tools for type checking, code metrics, framework-specific analysis, and quality heuristics via static parsing.
      100
      1
      MIT

    • LensPR

      kyrylopr
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that builds a dependency graph of your codebase, giving AI agents structural understanding to analyze impact, find context, and make safe modifications across languages and infrastructure.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity; for example, nanostores_store_impact is specifically for downstream dependency chains, while nanostores_store_subgraph handles bidirectional neighborhoods, and nanostores_scan_project focuses on project indexing versus nanostores_project_outline for summaries. The descriptions explicitly differentiate overlapping tools like nanostores_store_impact and nanostores_store_subgraph, preventing misselection.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with a 'nanostores_' prefix and descriptive verb_noun combinations (e.g., nanostores_clear_cache, nanostores_docs_search). The naming is predictable and uniform across all 12 tools, making them easily identifiable and readable without any deviations in style.

    Tool Count5/5

    With 12 tools, the count is well-scoped for the server's purpose of analyzing and debugging Nanostores projects. Each tool serves a specific role in static analysis, runtime monitoring, documentation, and performance tuning, covering a comprehensive workflow without being excessive or insufficient for the domain.

    Completeness5/5

    The tool set provides complete coverage for the Nanostores domain, including project scanning (nanostores_scan_project), runtime health checks (nanostores_runtime_overview), debugging (nanostores_store_activity), dependency analysis (nanostores_store_impact), documentation (nanostores_docs_search), and performance optimization (nanostores_find_noisy_stores). There are no obvious gaps; agents can handle all core workflows from setup to troubleshooting.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources