Voipbin MCP Server

voipbin-mcp PyPI v0.1.1

Published by voipbin — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for the VoIPbin CPaaS platform

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 52

Each tool and what it can reach — statically extracted from the published source.

  • send_emailnetwork egress
  • send_messagenetwork egress
  • create_aino sensitive capability
  • create_callno sensitive capability
  • create_campaignno sensitive capability
  • create_conferenceno sensitive capability
  • create_contactno sensitive capability
  • create_flowno sensitive capability
  • delete_campaignno sensitive capability
  • delete_conferenceno sensitive capability
Show 42 more tools ↓
  • delete_contactno sensitive capability
  • delete_flowno sensitive capability
  • get_activeflowno sensitive capability
  • get_agentno sensitive capability
  • get_aino sensitive capability
  • get_billingno sensitive capability
  • get_callno sensitive capability
  • get_campaignno sensitive capability
  • get_conferenceno sensitive capability
  • get_contactno sensitive capability
  • get_conversationno sensitive capability
  • get_customerno sensitive capability
  • get_emailno sensitive capability
  • get_extensionno sensitive capability
  • get_flowno sensitive capability
  • get_messageno sensitive capability
  • get_numberno sensitive capability
  • get_queueno sensitive capability
  • get_routeno sensitive capability
  • get_tagno sensitive capability
  • hangup_callno sensitive capability
  • list_activeflowsno sensitive capability
  • list_agentsno sensitive capability
  • list_aisno sensitive capability
  • list_billingsno sensitive capability
  • list_callsno sensitive capability
  • list_campaignsno sensitive capability
  • list_conferencesno sensitive capability
  • list_contactsno sensitive capability
  • list_conversationsno sensitive capability
  • list_emailsno sensitive capability
  • list_extensionsno sensitive capability
  • list_flowsno sensitive capability
  • list_messagesno sensitive capability
  • list_numbersno sensitive capability
  • list_queuesno sensitive capability
  • list_routesno sensitive capability
  • list_tagsno sensitive capability
  • stop_activeflowno sensitive capability
  • update_campaignno sensitive capability
  • update_contactno sensitive capability
  • update_flowno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/voipbin-mcp/badge.svg)](https://mcptrustchecker.com/registry/voipbin-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/voipbin-mcp"><img src="https://mcptrustchecker.com/registry/voipbin-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/voipbin-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan voipbin-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools