Skip to main content
Glama
Sign In
splinesreticulating

LiquidSoapMCP

by splinesreticulating
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to LiquidSoapMCP

No user-submitted related servers found.

    Related Servers

    • PineScript Docs

      paulieb89
      A
      license
      A
      quality
      B
      maintenance
      Provides comprehensive Pine Script v6 documentation and tools to help AI assistants look up functions, validate syntax, and generate accurate code. It enables linting, version conversion from v5 to v6, and deep conceptual analysis to prevent code hallucinations.
      10
      56 PyPI
      9
      MIT

    • strudel-mcp

      auto-duan
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides Strudel reference documentation as MCP tools for AI coding assistants, enabling function lookup, search, and syntax reference.
      3 npm
      AGPL 3.0

    • RealTest MCP Server

      cquillen
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides structured access to RealTest backtesting documentation and example scripts to help LLM agents generate accurate RealScript code. It offers tools for semantic search, authoritative function references, and verified script retrieval to prevent hallucinations.
      -

    • Typst MCP Server

      Raza3129
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI models to convert LaTeX snippets into Typst, validate Typst syntax, browse the official Typst documentation, and render Typst code to PNG images. This lets models verify typeset output and check code correctness before delivering it to users.
      -
    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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: version info, changelog, documentation sections, function search, examples, section listing, and script validation. Even list_sections and get_documentation have a natural complementary relationship without overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get, list, search, validate), with no mixing of conventions or vague verbs. The naming is predictable and readable.

    Tool Count5/5

    7 tools is well-scoped for a documentation and validation server. Each tool earns its place, covering the core use cases without redundancy or bloat.

    Completeness5/5

    The tool surface covers the domain comprehensively: version, changelog, documentation access, function lookup, examples, section navigation, and script validation. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources