Infobip MCP

Infobip Remote MCP Servers Documentation

MCP Servers Listed MIT

Is Infobip MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 63%
Last push 10d ago
Compare Infobip MCP
Suggest a correction

In detail: Infobip MCP scores 47.9/100 (Grade D), ranked #999 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.0/10; 63% of recent commits are signed; last pushed 2026-09-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Infobip MCP compares in MCP Servers

  1. #584 Lineai MCP Server 47.9 ±0
  2. #585 Openfate MCP 47.9 ±0
  3. #586 Infobip MCP 47.9 this agent
  4. #587 Appstore Connect MCP 47.9 ±0
  5. #588 MCP Victoriametrics 47.8 −0.1

Bars show each HVTrust score; the tick marks Infobip MCP’s 47.9.

Where the 47.9 comes from

HVTrust dimensions vs the MCP Servers average

47.9 / 100 · 100.0% confidence

Infobip MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.9 / 25
3.4 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.1 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
14.4 / 20
2.4 above avg 12.0
AdoptionLog-scaled stars · package downloads
3.7 / 20
3.6 below avg 7.3

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank rose 28 spots (#1020 → #992)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
47.0
Activity sub-score · out of 100
#586

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-27 06:32 UTC · Repo last pushed 10 days ago

Rank Trend

2026-08-11 2026-09-27

Activity & Reach

Stars
35
Forks
7
Last Push
2026-09-17
10 days ago
Commits (4 wk)
5
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #999

Analysis

Activity Inputs

47.0 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
4.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.0 / 10
OpenSSF Scorecard · scanned Sep 26, 2026
Signed Commits
63%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 6
Contributors 10
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 5
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Common questions about Infobip MCP

Public trust evidence for Infobip MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Infobip MCP publish package provenance?
No published build provenance is currently detected for Infobip MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Infobip MCP have an OpenSSF Scorecard?
Infobip MCP has an OpenSSF Scorecard score of 3.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Infobip MCP actively maintained?
Maintained. Last push was 10 days ago.
What license does Infobip MCP use?
Infobip MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Infobip MCP's commits signed?
62% of the last 100 commits to Infobip MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Infobip MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Infobip MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Infobip MCP?

For maintainers

HVTrust scores Infobip MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 21HVTrust 3Listed 2Scorecard 1Score 1Delisted 1MCP 1Surface 1
2026-09-25
Rank Moved
Rank rose 28 spots (#1020 → #992)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 446 spots (#570 → #1016)
2026-09-23
HVTrust Changed
HVTrust up 11.1pts (35.6 → 46.7)
2026-09-22
Newly Listed
First tracked at rank #570
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank rose 101 spots (#1113 → #1012)
2026-09-12
HVTrust Changed
HVTrust up 4.7pts (41.9 → 46.6)
2026-09-12
Activity Score Changed
Activity score up 14pts (31 → 44)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1093 → #1107)
2026-09-07
Rank Moved
Rank dropped 27 spots (#1058 → #1085)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1041 → #1058)
2026-09-05
Rank Moved
Rank dropped 38 spots (#1003 → #1041)
2026-09-04
Rank Moved
Rank dropped 26 spots (#977 → #1003)
2026-09-03
Rank Moved
Rank dropped 61 spots (#916 → #977)
2026-09-02
Rank Moved
Rank dropped 50 spots (#866 → #916)
2026-09-01
Rank Moved
Rank dropped 31 spots (#835 → #866)
2026-08-31
Rank Moved
Rank dropped 32 spots (#803 → #835)
2026-08-30
Rank Moved
Rank dropped 28 spots (#775 → #803)
2026-08-29
Rank Moved
Rank dropped 47 spots (#728 → #775)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.1/10
2026-08-28
Rank Moved
Rank rose 471 spots (#1199 → #728)
2026-08-28
HVTrust Changed
HVTrust up 24.1pts (18.7 → 42.8)
2026-08-27
Rank Moved
Rank dropped 13 spots (#1186 → #1199)
2026-08-26
Rank Moved
Rank dropped 47 spots (#1139 → #1186)
2026-08-16
Rank Moved
Rank dropped 55 spots (#1077 → #1132)
2026-08-15
Rank Moved
Rank dropped 17 spots (#1060 → #1077)
2026-08-12
Rank Moved
Rank rose 14 spots (#1064 → #1050)
2026-08-10
Rank Moved
Rank dropped 58 spots (#998 → #1056)
2026-08-08
Newly Listed
First tracked at rank #992

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 47.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/infobip-mcp.svg)](https://hvtracker.net/agents/infobip-mcp)
HTML:
<a href="https://hvtracker.net/agents/infobip-mcp"><img src="https://hvtracker.net/badge/infobip-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON