Skip to main content
Glama
mcp-qzone-safe

mcp-qzone-safe

by hoholi-668

Related Servers

Alternatives to mcp-qzone-safe

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with QQ through official bot APIs or personal accounts bridged via NapCat/OneBot v11, including status checks, target listing, bounded context retrieval, and plain-text sending to allowlisted conversations.
      5
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable models to read QQ messages, reply in group and private chats, send images and favorite stickers, poke users, and manage pacing, deduplication, and concurrency during ongoing chat tasks through a local SnowLuma OneBot interface.
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables MCP hosts to bridge with QQ via NapCat/OneBot 11, allowing whitelisted private messages to reach an agent with full tool access while group mentions are answered by a sandboxed pure LLM without system access.
      8
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A QQ toolbox MCP server that lets an agent manage Qzone posts (publish, list, like, comment, delete, set visibility), friend feeds, visitors, confession-wall submissions and scheduled posts, while also editing the bot's profile (avatar, nickname, signature, online status, status lookup) via OneBot/SnowLuma. It additionally sends images and text-to-speech voice clips into private or group chats and manages tool whitelists.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to fetch queued OneBot v11 QQ private and group messages, retrieve inbound images for vision-capable models, and send text, images, or files with request-id deduplication. Also exposes acknowledgment, message history, conversation and contact listing, delivery status, and bridge health so agents can drive a persistent SQLite-backed QQ message loop.
      MIT

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools target clearly distinct resources/actions (read posts, read comments, like, comment, list friends, write friend note). However, qzone_comment (write a comment) and qzone_comments (read comments) differ by a single 's' and both read as plausible for either meaning, a genuine misselection risk. The descriptions disambiguate once read, but the names alone do not.

    Naming Consistency3/5

    A two-prefix scheme (qzone_* for post interactions, friend_* for roster operations) is readable and roughly domain-driven. But within qzone_*, forms are mixed: verb phrases (qzone_see_posts, qzone_like, qzone_publish) alongside bare nouns (qzone_comments) and a near-duplicate singular/plural pair. friend_list/friend_note are noun phrases, adding to the inconsistency.

    Tool Count5/5

    Seven tools is well within the sweet spot for a scoped Qzone interaction server. Each tool maps to a distinct operation (view posts, view comments, like, comment, list friends, annotate friend, publish) with no filler.

    Completeness4/5

    The read-and-interact lifecycle is covered: fetch posts, fetch comments, like, comment/reply, plus a friend roster and note-writing flow with whitelist constraints. Gaps are minor but real: no unlike, no delete/edit of comments or posts, and qzone_publish is hard-disabled, so post creation is a deliberate dead end agents cannot work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues