Skip to main content
Glama
han0420

MCP Dev Standards

by han0420
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Dev Standards

No user-submitted related servers found.

    Related Servers

    • MCP Standards Server

      williamzujkowski
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server that provides intelligent, context-aware access to development standards, enabling LLMs to automatically select and apply appropriate standards based on project requirements.
      3
      MIT

    • PAELLADOC

      jlcases
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server that implements AI-First Development framework principles, allowing LLMs to interact with context-first documentation tools and workflows for preserving knowledge and intent alongside code.
      336
      AGPL 3.0
    • CodeAlive MCP by CodeAlive-AI

      CodeAlive MCPofficial

      CodeAlive-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.
      90
      MIT

    • Lucidity MCP

      hyperb1iss
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enhances AI-generated code quality through comprehensive analysis across 10 critical dimensions, helping identify issues before they become problems.
      1
      90
      Apache 2.0

    • Codebase MCP Server

      cmaujean
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that analyzes application codebases with real-time file watching, providing AI assistants like Claude with deep insights into project structure, code patterns, and architecture.
      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

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: resolve-standard-id searches by keyword, get-standard-docs retrieves content by ID, and list-standards provides a browsable overview. There is no overlap between searching, fetching, and listing.

    Naming Consistency5/5

    All tool names follow the same verb_noun hyphenated pattern: resolve-standard-id, get-standard-docs, list-standards. The verbs and objects are consistent and readable.

    Tool Count5/5

    Three tools are well-scoped for a read-only standards documentation server. The set covers the essential operations—search, fetch, and list—without unnecessary extras.

    Completeness5/5

    The tool surface covers the full lifecycle for a documentation server: discovering standards (list), finding specific ones (resolve), and retrieving details (get). There are no obvious dead ends; the dependency between resolve and get is clearly documented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources