Skip to main content
Glama
rajesh-taylor

@refueler/mcp-server

Related Servers

Alternatives to @refueler/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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
      Not graded
      quality
      B
      maintenance
      Secure file exchange MCP server enabling AI agents to upload, share, fetch, and revoke files with SHA-256 verification, malware scanning, expiry, access restrictions, and human approval workflows.
      13 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      54 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.
      14 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables secure file transfers (FTP/FTPS/SFTP) with built-in SHA-256 verification proofs, ensuring every upload and download is cryptographically verified for integrity.
      13
      73 npm
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    With a single tool there is no possibility of misselection or overlapping purpose. Its intent (fetch server capabilities/rate card before sending) is unambiguous.

    Naming Consistency4/5

    The lone name refueler_capabilities is snake_case and namespaced, which is readable and predictable. It is noun-based rather than a verb_noun action pattern, but consistency cannot really be violated with one tool.

    Tool Count2/5

    A single tool is far too thin for a server whose description implies a send workflow. There is no operation to actually do anything, making the surface feel like a stub.

    Completeness1/5

    The tool explicitly exists as a precondition for 'any send', yet no send, quote, status, or account operation is exposed. The advertised domain is essentially uncovered, leaving agents at a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues