Envoyez des SMS marketing et transactionnels directement depuis vos agents IA via l'API SMS Vert Pro — opérateur français de SMS Pro depuis 2008. ## Outils exposés (10) - **send_sms** — Envoi de SMS unitaire ou en masse, immédiat ou programmé - **check_credits** — Consultation du solde de crédits SMS - **get_delivery_report** — Rapport de délivrabilité d'une campagne - **get_responses** — Réponses reçues (SMS 2-way / bidirectionnel) - **verify_number** — Vérification HLR de la validité des numéros - **get_blacklist** — Liste des numéros ayant envoyé STOP (RGPD) - **cancel_sms** — Annulation d'une campagne programmée + restitution des crédits - **generate_otp** — Envoi d'un code OTP pour authentification 2FA - **verify_otp** — Vérification d'un code OTP saisi - **count_sms_parts** — Estimation locale du nombre de SMS et du coût avant envoi (gratuit, GSM-7 only) ## Cas d'usage - **Notifications transactionnelles** : confirmation de commande, rappel de RDV, alertes - **Marketing** : campagnes promotionnelles avec mention STOP automatique - **Authentification 2FA** : codes OTP par SMS, validité 5 minutes - **Communication client** : SMS 2-way avec gestion des réponses - **Estimation préalable** : calcul du coût d'une campagne avant envoi via count_sms_parts ## Démarrage rapide 1. Créez un compte gratuit sur [smsvertpro.com](https://www.smsvertpro.com/espace-client/?type=1) 2. Générez votre token API sur [/api/doc-v2.php](https://www.smsvertpro.com/api/doc-v2.php) 3. Collez le token dans la config Smithery 4. Demandez à votre agent IA : *"Envoie un SMS à 33612345678 pour confirmer le RDV de demain 14h"* ## Sécurité & conformité - Hébergé en **Union Européenne** (conforme RGPD) - Token API révocable à tout moment - Logs de toutes les actions sensibles + email de notification - Gestion automatique des opt-out (STOP 36173) - Plus de **5 000 entreprises** clientes depuis 2008 ## Aussi disponible en self-host Si vous préférez héberger le serveur MCP vous-même : [TypeScript](https://github.com/3-bees-online/mcp-server-smsvertpro-typescript), [Python](https://github.com/3-bees-online/mcp-server-smsvertpro-python).

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (3167 ms); slow response -1.
Protocol revision	10/10	Speaks the current MCP revision 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	14.52/15	30/31 probes succeeded over 30 days (97%).
Tool declaration	10/10	Lists 10 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (3167 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 96% of peers; This listing 88 · peer median 81
Latency: Faster than 6% of peers; This listing 1,098 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Live MCP endpoint −1 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (3167 ms); slow response -1.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/three-bees-online/smsvertpro/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/three-bees-online/smsvertpro/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.smsvertpro.com/integration-ia/

Listed at (smithery)

https://www.smsvertpro.com/integration-ia/