Skip to main content
Glama
joestar817

legado-mcp-server

by joestar817
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to legado-mcp-server

No user-submitted related servers found.

    Related Servers

    • JLC_EDA-MCP

      mayjack0312
      A
      license
      C
      quality
      B
      maintenance
      Enables interaction with EasyEDA Pro by exposing 760 official API methods as MCP tools, along with plugin import and browser console debugging capabilities.
      500
      Apache 2.0

    • codex-bridge

      Fanch-hui
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables web-based ChatGPT and Qwen Studio to connect to local agents and projects, providing secure local file read/write, task execution, and approval workflows through a unified MCP bridge.
      67
      Apache 2.0

    • silly-tavern-mcp

      LoveMaker-art
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to control SillyTavern through MCP tools for managing characters, chats, worldbooks, prompt assembly, extensions, plugins, snapshots, and runtime state.
      60
      MIT

    • TalkAPI

      prakhar7824
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables conversational API testing via MCP, allowing users to make HTTP requests, decode JWT tokens, and validate JSON schemas through natural language.
      -

    • qq-music-mcp

      wangkezun
      A
      license
      A
      quality
      D
      maintenance
      Integrates QQ Music API with MCP, enabling LLMs to search music, retrieve song details, lyrics, and playback URLs.
      10
      4
      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

    D1.9/5.0

    Scored across 31 tools

    Disambiguation2/5

    Many tools have very similar names (e.g., book_source_save and book_source_save_many, rss_source_save and rss_source_save_many, etc.) and most lack descriptions, making it difficult to distinguish their distinct purposes. This ambiguity risks tool misselection by an agent.

    Naming Consistency5/5

    All tool names follow a consistent <object>_<action> pattern (e.g., book_search, book_delete, book_source_save, legado_ping). No mixing of conventions (camelCase or verb styles) is observed, providing a predictable naming scheme.

    Tool Count3/5

    With 31 tools, the server covers multiple domains (books, book sources, RSS sources, replace rules, config), which is comprehensive but on the heavier side. Some tools may be redundant (e.g., separate save and save_many), suggesting slight over-scoping.

    Completeness4/5

    The tool set covers core CRUD and lifecycle operations for books, sources, and rules, plus debugging and configuration. Minor gaps exist (e.g., no explicit book update tool, though book_save may serve that purpose), but overall the surface is well-rounded.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources