Skip to main content
Glama
TheoryofShadows

@mcpx-digital/readme-score

by TheoryofShadows
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @mcpx-digital/readme-score

No user-submitted related servers found.

    Related Servers

    • mcp-repo-health

      ashwinmridul
      A
      license
      B
      quality
      C
      maintenance
      Scores local git repositories for README substance, license, package description, TypeScript config, tests, and GitHub Actions, providing a numbered hygiene report.
      2
      MIT

    • md-lint

      TheoryofShadows
      A
      license
      A
      quality
      C
      maintenance
      Lints local Markdown files or whole directory trees for broken relative links and images, empty link targets or text, heading hierarchy problems, and common README issues. Only relative targets on disk are checked, so external http(s) links are never fetched.
      2
      MIT

    • MCP Docs Server

      Unlock-MCP
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides direct access to local documentation files through simple search and overview tools, enabling LLMs to query project-specific markdown documentation without requiring vector databases or RAG pipelines.
      MIT

    • codescan-mcp

      yifanyifan897645
      A
      license
      Not graded
      quality
      D
      maintenance
      Scans codebases for TODOs, FIXMEs, code complexity, file stats, and dependencies, generating a health report with a letter grade. Zero configuration required.
      33 npm
      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.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools are mostly easy to distinguish: score_readme produces an overall score, suggest_improvements produces recommendations, and check_readme_links verifies link resolution. However, score_readme already includes relative link validity in its scoring, so an agent could be uncertain whether to call score_readme or check_readme_links for link checking.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case verb-object pattern: score_readme, suggest_improvements, check_readme_links. The naming makes the action and target predictable across the entire set.

    Tool Count5/5

    Three tools is well-scoped for a focused README-scoring server. Each tool covers a distinct stage of the workflow—evaluating, suggesting improvements, and validating links—without unnecessary bloat.

    Completeness5/5

    The toolkit covers the complete local README workflow: scoring, receiving concrete improvement suggestions, and checking relative link integrity. Since the server explicitly targets local README files, there are no major missing operations within its stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources