Skip to main content
Glama
theletterf

Vale MCP Server

by theletterf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Vale MCP Server

No user-submitted related servers found.

    Related Servers

    • markdownlint-mcp

      ernestgwilsonii
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with the ability to lint, validate, and auto-fix Markdown files to ensure compliance with established Markdown standards and best practices.
      6
      MIT

    • RuboCop MCP Server

      ishtiaque05
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides RuboCop and Rails linting capabilities to AI assistants like Claude and Cursor, allowing them to lint, auto-correct, and manage Ruby code style violations.
      MIT

    • slop-guard

      Horst53236
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to score prose from 0–100 for formulaic AI writing patterns using rule-based linting, returning diagnostics such as band labels, violations with context, and advice. It can analyze inline text or files without API calls or LLM judges.
      -

    • slop-guard

      camila02800
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to analyze text strings or files for formulaic AI writing patterns, returning a 0–100 score, band label, specific violations with context, and concrete advice. It performs this rule-based linting locally without LLM judges or API calls.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: check_file performs linting, vale_status checks installation status, and vale_sync downloads styles. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task at hand.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: check_file, vale_status, and vale_sync. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count5/5

    With 3 tools, the server is well-scoped for its purpose of Vale integration. Each tool earns its place by covering essential functions: installation check, style management, and linting, avoiding unnecessary complexity or redundancy.

    Completeness5/5

    The tool surface provides complete coverage for the Vale domain: vale_status handles setup verification, vale_sync manages style dependencies, and check_file performs the core linting operation. There are no obvious gaps, ensuring agents can handle the full workflow from installation to linting.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources