Skip to main content
Glama
lazymac2x

lazymac-mcp

by lazymac2x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to lazymac-mcp

No user-submitted related servers found.

    Related Servers

    • WhenLabs/When

      WhenLabs-org
      A
      license
      A
      quality
      D
      maintenance
      A unified developer toolkit for AI-assisted workflows. Task timing, doc drift detection, env validation, secret scanning, port conflict resolution, AI context generation, and license auditing — one MCP server, one install.
      7
      3
      MIT

    • ts-mcp-tools

      codedonkeyuk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables developers to build and deploy MCP servers with multiple modular tools bundled into a single executable file.
      MIT

    • yala

      MalekYala
      A
      license
      A
      quality
      C
      maintenance
      MCP server exposing 570 config-driven dev tools across plan, develop, QA, feedback automation, and deploy stages, with meta-tools for searching and running them via natural language.
      4
      MIT

    • Thask

      kimgh06
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides 25 tools for AI agents to query and modify a dependency graph, enabling impact analysis and provenance tracking for AI-assisted development.
      8
      MIT

    • OneTool MCP

      beycom
      A
      license
      Not graded
      quality
      C
      maintenance
      One MCP for developers — no tool tax, no context rot. 100+ tools including Brave, Google, Tavily, Context7, Excalidraw, AWS, Excel, Database, Playwright, Chrome DevTools, and more. Install once, access everything.
      24
      GPL 3.0
    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

    C2.3/5.0

    Scored across 41 tools

    Disambiguation2/5

    Several tools have heavily overlapping purposes, such as ai_rate_limit_tracker vs ai_provider_status, ai_cost_calculator vs llm_pricing, k_address_tools vs k_address_geocoder, and k_company_lookup vs k_business_validator. With 41 utilities, it is easy to select the wrong tool.

    Naming Consistency3/5

    All names are lowercase snake_case, but conventions are mixed: some are noun objects (qr_code, password_strength), some use prefixes (ai_, k_, llm_), and some use suffixes like _tracker, _calculator, or _tools. Not chaotic, but there is no consistent verb_noun action pattern.

    Tool Count2/5

    41 tools is far too many for a coherent toolkit stanpoint. The count feels like an indiscriminate grab bag rather than a purpose-scoped server, especially with several overlapping sub-domains.

    Completeness2/5

    There is no clear overarching domain, so it is impossible to have complete coverage. Within the various mini-areas, tools are often single-purpose and lack depth, e.g., no CRUD-style workflows or follow-up operations for most utilities.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources