Skip to main content
Glama
snowluma-file-sender

snowluma-file-sender

by ktouch10

Related Servers

Alternatives to snowluma-file-sender

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely transfer files between machines via encrypted, expiring share links, with tools for upload, download, status checks, and link management.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to send and receive files securely via JustDrop, with end-to-end encryption, QR codes, and no server-side storage.
      4
      124 npm
      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
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to price, send, and track encrypted file transfers, with files chunked, encrypted, and hashed locally before any network relay, and to retrieve signed collection receipts. It supports prepaid credit pools and gives agents a privacy-first transfer capability within their own trust domain.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      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
      A
      maintenance
      Enables AI agents to split large files, zips, or folders into size-capped parts with SHA-256 checks, verify or regenerate missing parts, and rebuild the original across platforms so handoffs respect strict per-file upload limits.
      8
      1
      -

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: prepare creates a deliveryId, send_file sends an already prepared file, delivery_status checks local status only, and file_secretary_help documents the workflow. The boundaries between preparation, sending, and status checking are explicit.

    Naming Consistency3/5

    All names use snake_case, but the convention is mixed: send_file and prepare_file are verb_noun, while delivery_status and file_secretary_help are noun-based. The names remain readable and reasonably predictable.

    Tool Count5/5

    Four tools are well-scoped for a narrow file-sending workflow: help, prepare, send, and status. Each tool appears to earn its place without unnecessary surface area.

    Completeness4/5

    The set covers the core lifecycle from preparing a file to sending it and checking delivery status, plus workflow help. Minor gaps exist around canceling, listing deliveries, or handling resend/busy cases beyond the documented prohibition.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues