uni-msg

endpoint

https://uni-msg.com/mcp/v1

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is uni-msg live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is uni-msg free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does uni-msg have?

13 tools: list_conversations, send_message, get_device_status, request_pairing_code, list_devices, list_contacts, connect_device, create_device, ….

Is uni-msg safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_conversations reads auth-required 26h ago

  List recent WhatsApp conversations for a device — who has been in touch and when. Use this to find the "peer" value that read_thread needs.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number",
        "description": "Default 50, max 500."
      },
      "search": {
        "type": "string",
        "description": "Match against name or number."
      },
      "deviceId": {
        "type": "string",
        "description": "Optional. Omit to span all devices."
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy
• send_message sends messages auth-required never probed

  Send a WhatsApp text message. The recipient may be a phone number in international format without "+" (e.g. 971501234567), or a JID for a group (…@g.us) or LID (…@lid). Sends immediately — there is no undo, so confirm the recipient with the user before calling this.

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "required": [
      "deviceId",
      "to",
      "content"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Phone number in international format, or a JID."
      },
      "content": {
        "type": "string",
        "description": "Message text, up to 4096 characters."
      },
      "deviceId": {
        "type": "string",
        "description": "Which device sends it. See list_devices."
      }
    },
    "additionalProperties": false
  }

  arguments 23 lines copy
• get_device_status reads auth-required 11h ago

  Check one device: whether it is connected, and when it was last seen. Use when a send fails, to tell a disconnected device from a bad recipient.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "deviceId"
    ],
    "properties": {
      "deviceId": {
        "type": "string",
        "description": "Device id, e.g. dev_abc123"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• request_pairing_code changes data auth-required never probed

  Issue a fresh pairing code for a device that is already connecting. Use this when the previous code expired — it is cheaper and more reliable than tearing the session down and starting again.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "deviceId"
    ],
    "properties": {
      "deviceId": {
        "type": "string"
      }
    },
    "additionalProperties": false
  }

  arguments 12 lines copy
• list_devices reads auth-required 26h ago

  List the WhatsApp devices on this account with their connection status. Use this first — every send needs a deviceId, and only a device whose status is "connected" can deliver a message.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• list_contacts reads auth-required 26h ago

  List saved contacts, optionally filtered by a search term.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number",
        "description": "Default 25, max 100."
      },
      "search": {
        "type": "string",
        "description": "Match against name or number."
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• connect_device changes data auth-required never probed

  Step 2 of 3. Starts a session and returns an 8-character pairing code (and sometimes a QR string). Give the user the code and these exact instructions: on the phone holding that number, open WhatsApp → Settings → Linked devices → Link a device → "Link with phone number instead", then type the code. The code expires in about two minutes; if it lapses, call request_pairing_code for a fresh one rather than connect_device again. After they enter it, poll get_device_status until it reports connected.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "deviceId"
    ],
    "properties": {
      "deviceId": {
        "type": "string",
        "description": "From create_device or list_devices."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• create_device changes data auth-required never probed

  Register a new WhatsApp number so it can be paired. Step 1 of 3: create_device, then connect_device to get a pairing code, then the user enters that code on their phone. Creating a device may consume a slot on the account's plan, so check list_devices first rather than creating a duplicate for a number that already exists.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "required": [
      "name",
      "phoneNumber"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "A label for this device, e.g. \"Sales line\"."
      },
      "phoneNumber": {
        "type": "string",
        "description": "The number to pair, in international format, e.g. +971501234567."
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy
• disconnect_device changes data auth-required never probed

  End a device session. The number stays registered and can be reconnected later, but it stops sending and receiving immediately, so confirm with the user before calling this.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "deviceId"
    ],
    "properties": {
      "deviceId": {
        "type": "string"
      }
    },
    "additionalProperties": false
  }

  arguments 12 lines copy
• send_media sends messages auth-required never probed

  Send an image, video, audio clip or document by public URL. The URL must be reachable by uni-msg — a local file path will not work. Sends immediately; confirm the recipient first.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940

  {
    "type": "object",
    "required": [
      "deviceId",
      "to",
      "kind",
      "mediaUrl"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Phone number in international format, or a JID."
      },
      "kind": {
        "enum": [
          "image",
          "video",
          "audio",
          "document"
        ],
        "type": "string"
      },
      "caption": {
        "type": "string",
        "description": "Optional. Ignored for audio."
      },
      "deviceId": {
        "type": "string"
      },
      "fileName": {
        "type": "string",
        "description": "Optional, for documents."
      },
      "mediaUrl": {
        "type": "string",
        "description": "Publicly reachable https URL."
      }
    },
    "additionalProperties": false
  }

  arguments 40 lines copy
• upsert_contact changes data auth-required never probed

  Create a contact, or update it if the number already exists. Matching is by phone number, so this will not create a duplicate.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "phoneNumber"
    ],
    "properties": {
      "name": {
        "type": "string"
      },
      "email": {
        "type": "string"
      },
      "phoneNumber": {
        "type": "string",
        "description": "International format, no \"+\"."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• read_thread reads auth-required 11h ago

  Read the message history with one contact or group. "peer" is the other party's phone number or JID, as returned by list_conversations. Returns newest first; use page to go further back.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "required": [
      "deviceId",
      "peer"
    ],
    "properties": {
      "page": {
        "type": "number",
        "description": "Default 1."
      },
      "peer": {
        "type": "string",
        "description": "Phone number or JID of the other party."
      },
      "limit": {
        "type": "number",
        "description": "Default 30, max 100."
      },
      "deviceId": {
        "type": "string"
      }
    },
    "additionalProperties": false
  }

  arguments 25 lines copy
• list_groups reads auth-required 11h ago

  List WhatsApp groups a device belongs to, with their JIDs. Use the JID as the "to" value in send_message to post to a group.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "deviceId"
    ],
    "properties": {
      "deviceId": {
        "type": "string"
      }
    },
    "additionalProperties": false
  }

  arguments 12 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.