Skip to main content
Glama
Sign In
dayuan-lite

dayuan-lite

by lighters
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dayuan-lite

No user-submitted related servers found.

    Related Servers

    • wecom-msg-audit-mcp

      deadmau5v
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to securely access and search enterprise WeChat (WeCom) chat records with full decryption and auditing, supporting message retrieval, decryption, local storage, and querying via MCP tools.
      9
      3
      MIT

    • noteford-community

      Followhongyun
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables authorized AI clients to search locally stored WeChat conversations, media, and attachments, retrieve original-message context, and cite evidence through a local stdio MCP interface.
      AGPL 3.0

    • wxq

      vpcoderli
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query local WeChat chat data through read-only MCP tools, including sessions, messages, contacts, search, and statistics, with everything processed locally.
      85 PyPI
      4
      MIT

    • yan

      lyqi712
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to read local WeChat data through an existing WxLens HTTP service, so users can find messages, extract a person's statements, summarize discussions, scan multiple groups, and read related articles or attachments.
      40
      5
      MIT

    • wechat-mcp

      myWorldmakerTonyczk
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to control the Windows WeChat desktop app, including reading conversations, sending messages, searching contacts, and monitoring new messages via UI automation.
      -
    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.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    The async lifecycle (read_start → read_result → read_reply) is clearly separated, and wecom_read is a distinct synchronous read path. The main overlap is between capabilities and status (both are informational diagnostics), plus a potential question of when to use read_start versus wecom_read, though the descriptions do draw the line at async remote tasks versus direct token reads.

    Naming Consistency4/5

    All tools share the dayuan_ prefix and snake_case, making names predictable and collocation-friendly. The only deviation is word order: read_start/read_result/read_reply put the action verb first, while wecom_read puts the resource first, and capabilities/status are noun-only.

    Tool Count4/5

    Six tools is a well-scoped count for a read-only gateway whose purpose is to expose a query lifecycle plus one direct read path. Four of the six slots are consumed by the async task lifecycle, but each of those serves a necessary step (submit, poll, clarify).

    Completeness3/5

    The read lifecycle, capability discovery, and WeCom data reads are covered, but there is no way to cancel or abandon a submitted query, no listing of in-flight request_ids, and no continuation mechanism for oversized results. File and attachment reads are explicitly excluded, which is defensible but leaves a real gap for document workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources