Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability40
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 121 tokens (~121/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the com.infobip/mcp server?

com.infobip/mcp is a hosted endpoint at https://mcp.infobip.com/search/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.infobip.com

# add to Claude Code
claude mcp add --transport http com-infobip-mcp 'https://mcp.infobip.com/search/sse'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-infobip-mcp": {
      "url": "https://mcp.infobip.com/search/sse"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-infobip-mcp": {
      "type": "http",
      "url": "https://mcp.infobip.com/search/sse"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-infobip-mcp]
url = "https://mcp.infobip.com/search/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-infobip-mcp": {
      "type": "remote",
      "url": "https://mcp.infobip.com/search/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-infobip-mcp --url 'https://mcp.infobip.com/search/sse' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-infobip-mcp:
    url: "https://mcp.infobip.com/search/sse"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-infobip-mcp": {
      "Transport": "http",
      "Url": "https://mcp.infobip.com/search/sse"
    }
  }
}
# add to Vellum
assistant mcp add com-infobip-mcp -t streamable-http -u 'https://mcp.infobip.com/search/sse'
// mcp.json
{
  "mcpServers": {
    "com-infobip-mcp": {
      "type": "http",
      "url": "https://mcp.infobip.com/search/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Sept 26 0
    • Server version: 1.8.1 → 1.8.2 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Aug 26 0
    • Server version: 1.8.0 → 1.8.1 functional
  • 3 Aug 26 0
    • Schema quality: 148 → 121 functional
    • “explore” dropped the optional parameter “fuzziness” cosmetic
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://mcp.infobip.com/search/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.infobip.com CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 17 Nov 2025 16 Nov 2026 RSA 2048 SHA256-RSA 3c452f93f894ec89f96ca6e5c427192
SANs: *.infobip.com, infobip.com
CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA b259422ced9812a15a04e99528a0efa
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.infobip.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
infobip.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 404

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.infobip.com/search/sse Verified 200
http (plaintext) http://mcp.infobip.com/search/sse HTTPS enforced 302 https://mcp.infobip.com/search/sse
MCP tools · 1 exposed · ~86 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explore ~86

# Explore Infobip Documentation Use semantic search to explore the [Infobip documentation hub](https://www.infobip.com/docs), a comprehensive collection of product documentation, practical use cases, and general platform information designed to help both new and advanced users find resources and inspiration for interacting with end-users.

NameTypeReqDescription
querystringyesText query to search through Infobip documentation pages.

No output schema declared.

No examples provided.

Common questions

What is the com.infobip/mcp server?

com.infobip/mcp is listed in the public MCP registry as com.infobip/mcp. Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more. This page covers its hosted endpoint (https://mcp.infobip.com/search/sse).

Is the com.infobip/mcp server safe to use?

com.infobip/mcp scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.infobip/mcp server expose?

com.infobip/mcp exposes 1 tool: explore. Their descriptions and schemas cost roughly 86 tokens of context every time the server is loaded.

Does the com.infobip/mcp server require authentication?

No. We connected to com.infobip/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.infobip/mcp server still maintained?

com.infobip/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.