Skip to content

MSG91 MCP server

com.msg91.mcp/mcpmcp.msg91.comstreamable-httpv1.0.0Scanned

Find and call the right MSG91 API for SMS, OTP, WhatsApp, Email and Voice.

5 tools: 1 can delete or cancel things, 2 change things and 2 only read.

Tools: 1 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 3
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the MSG91 MCP server can do

The MSG91 MCP server is published by mcp.msg91.com, a domain the MCP Registry verified. It has 5 tools. It can delete or cancel things (1 tool: call_any_api_of_msg91) and create or change data (2 tools: call_any_read_api_of_msg91 and quickstart-msg91). 2 tools only read.

2 tools read private data (search_msg91_docs and get_msg91_api_docs); 3 tools bring in text other people can write (get_msg91_api_docs, call_any_api_of_msg91 and call_any_read_api_of_msg91); 1 tool can send data out of your system (call_any_read_api_of_msg91). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Deletes or cancels 1Claude Code: deny
  • call_any_api_of_msg91Send a POST, PUT, PATCH or DELETE request to any MSG91 API endpoint for the user and return its response.Reads text others writeNo findings

    Why it is in this group

    • The name "call_any_api_of_msg91" says "call": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Send a POST, PUT, PATCH or DELETE request to any MSG91 API endpoint for the user and return its response. Use it once you know the exact endpoint: look it up with get_msg91_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-msg91 skill first: it explains which tool to use when. For GET requests use call_any_read_api_of_msg91. Pass the full url with path variables filled in, the headers the docs list, query params in `query` (not in the url) and the JSON body in `body`. For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.

    Annotations the server declares

    • title: Write to MSG91 API
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • call_any_read_api_of_msg91Read from any MSG91 API endpoint with a GET request for the user and return its response.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "call_any_read_api_of_msg91" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "call_any_read_api_of_msg91" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "call_any_read_api_of_msg91" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Read from any MSG91 API endpoint with a GET request for the user and return its response. Use it once you know the exact endpoint: look it up with get_msg91_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-msg91 skill first: it explains which tool to use when. For POST, PUT, PATCH and DELETE use call_any_api_of_msg91. Pass the full url with path variables filled in, the headers the docs list, and query params in `query` (not in the url). For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.

    Annotations the server declares

    • title: Read from MSG91 API
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • quickstart-msg91Quickstart for the MSG91 API Call this to load the full instructions for this skill before doing the task.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Quickstart for the MSG91 API Call this to load the full instructions for this skill before doing the task.

    Annotations the server declares

    • title: Quickstart Msg91
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • get_msg91_api_docsBrowse the MSG91 API docs, one level at a time.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_msg91_api_docs" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_msg91_api_docs" says "get" and "doc": it reads documents.
    • private-dataThe description's first sentence says "browse" and "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse the MSG91 API docs, one level at a time. Call it without arguments to get the top level: the modules and pages with a short description and the endpoints they hold. Call it with `path` set to a module's or page's link (or path) to get what is inside it; each listing links the next level. Call it with `path` set to an endpoint's link ending in ".openapi.yml" to get that endpoint as an OpenAPI file: method, url, headers, query params, path variables, a request body example and sample responses. Fetch only the level you need.

    Annotations the server declares

    • title: Get MSG91 API docs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_msg91_docsSearch the MSG91 documentation with a natural-language question.Reads private dataNo findings

    Why it is in this group

    • The name "search_msg91_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_msg91_docs" says "search" and "doc": it reads documents.
    Description, as the server wrote it
    Search the MSG91 documentation with a natural-language question. Returns the most relevant passages with their page URLs.

    Annotations the server declares

    • title: Search MSG91 docs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__server__call_any_read_api_of_msg91"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.msg91.com/oauth/6acf2d8c00875edfe408c69d
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.msg91.com/mcp: tools/list returned 5 tools to an anonymous client, including call_any_api_of_msg91 (destructive), call_any_read_api_of_msg91 (write), quickstart-msg91 (write)

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • Tools that change things, listed without credentials: 1 to 3
    • RFC 9728 protected resource metadata: none to https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.msg91.com/oauth/6acf2d8c00875edfe408c69d
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  2. Nov 14, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp to none
    • RFC 9728 protected resource metadata: https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mcp.msg91.com/oauth/6acf2d8c00875edfe408c69d to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  3. Nov 7, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.msg91.com/oauth/6acf2d8c00875edfe408c69d
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "call_any_read_api_of_msg91" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "call_any_read_api_of_msg91" says "call": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 3; RFC 9728 protected resource metadata: none -> https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://mcp.m…View diff
    • Tools that change things, listed without credentials: 1 to 3
    • RFC 9728 protected resource metadata: none to https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.msg91.com/oauth/6acf2d8c00875edfe408c69d
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp to none
    • RFC 9728 protected resource metadata: https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mcp.msg91.com/oauth/6acf2d8c00875edfe408c69d to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  3. Tools2 added.+2 addedView diff
  4. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://mcp.msg91.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.msg91.com/oauth/6acf2d8c00875edfe408c69d
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http server https://mcp.msg91.com/mcp
claude mcp add --transport http server https://mcp.msg91.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__server__search_msg91_docs",
      "mcp__server__get_msg91_api_docs"
    ],
    "ask": [
      "mcp__server__call_any_read_api_of_msg91",
      "mcp__server__quickstart-msg91"
    ],
    "deny": [
      "mcp__server__call_any_api_of_msg91"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as server. Review it before you use it.

Capability tags behind 4 rules
  • mcp__server__search_msg91_docs private-data
  • mcp__server__get_msg91_api_docs private-data, untrusted-input
  • mcp__server__call_any_api_of_msg91 untrusted-input
  • mcp__server__call_any_read_api_of_msg91 untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.msg91.mcp/mcp/verify?hash=597d9ef65b36f2abe00ff50885d72c833031b22cc05445c6ddc8d0be4c3affd6" | jq -e '.changed == false'

Pinned hash 597d9ef65b36, from Nov 12, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.msg91.mcp/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.msg91.mcp/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.msg91.mcp/mcp.svg)](https://radar.anlyon.com/servers/com.msg91.mcp/mcp)

Source: MCP Registry · repository. Synced Oct 30, 2026, 12:17 UTC.

MSG91 MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MSG91 MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the MSG91 MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: call_any_api_of_msg91.

Can the MSG91 MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MSG91 MCP server have?

5 tools: 1 destructive, 2 write, 2 read. call_any_api_of_msg91, call_any_read_api_of_msg91, quickstart-msg91, search_msg91_docs and get_msg91_api_docs.

Does the MSG91 MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MSG91 MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): call_any_read_api_of_msg91.

Has the MSG91 MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.