Skip to main content
Glama
privacyflow-app

PrivacyFlow MCP Server

Official
by privacyflow-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to PrivacyFlow MCP Server

No user-submitted related servers found.

    Related Servers

    • BTB

      jaytel0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables personal agents to exchange durable messages through permanent identities, shared private rooms, direct messages, and owner-approved external contacts while preserving history and supporting push/webhook wake-ups.
      MIT

    • pigeonpost

      bekirdag
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides asynchronous messaging infrastructure for AI agents, enabling them to get permanent addresses and send/receive encrypted messages via MCP tools.
      1
      MIT

    • signal-mcp-remote

      febin-micheal
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables remote Model Context Protocol clients to securely read, search, and send Signal Messenger messages through an HTTP interface backed by a personal signal-cli daemon.
      MIT

    • @wirebox-sh/mcp

      wirebox-sh
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to send and receive iMessages and emails, and manage agent identities, in MCP-compatible clients.
      6
      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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action: health check, API key validation, app listing, polling incoming messages, and sending messages. Descriptions clearly differentiate the purpose of each tool, with no meaningful overlap.

    Naming Consistency5/5

    All tools follow a consistent pattern: the 'privacyflow' prefix followed by a verb_noun structure (check_health, verify_api_key, list_apps, poll_messages, send_messages). This uniform naming makes the toolset predictable and easy to navigate.

    Tool Count5/5

    With exactly 5 tools, the server is well-scoped for a messaging integration service. Each tool covers a necessary operation (health, auth, discovery, receive, send) without unnecessary bloat or redundancy.

    Completeness4/5

    The toolset covers the core lifecycle of a messaging service: authentication, app discovery, sending, and receiving messages. Minor gaps exist (e.g., no explicit message acknowledgment or per-app filtering on poll), but these are reasonable workarounds and do not cripple the primary workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources