SMS Vert Pro
REMOTE · WWW.SMSVERTPRO.COM
French SMS platform for AI agents: bulk & scheduled SMS, OTP, delivery reports, replies, STOP list.
Available components
Last scanned (20 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Communication
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 725 tokens (~72/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_sms" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://www.smsvertpro.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sms.artecka.online | CN=YR2,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | RSA 4096 | SHA256-RSA | 508b542e2ddb72185d5132a2dd1a3e343db |
| SANs: artecka.smsvertpro.com, champion.smsvertpro.com, servicetelpro.smsvertpro.com, sms.artecka.online, smsvertpro.com, www.smsvertpro.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.smsvertpro.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| smsvertpro.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://www.smsvertpro.com/.well-known/oauth-protected-resource/mcp"
Bearer realm="mcp", resource_metadata="https://www.smsvertpro.com/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://www.smsvertpro.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.smsvertpro.com/mcp |
| Authorisation server | https://www.smsvertpro.com/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.smsvertpro.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://www.smsvertpro.com/mcp/ | Inconclusive | 405 |
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 →
cancel_sms ~51
Annule une campagne SMS non encore envoyée et recrédite le compte.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | ID de la campagne |
| sms_id | string | – | ID du SMS précis (optionnel) |
No output schema declared.
No examples provided.
check_credits ~29
Consulte le solde de crédits SMS. 1 crédit = 1 SMS de 160 caractères.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
count_sms_parts ~193
Calcule localement combien de SMS (parts) un message va consommer, sans rien envoyer ni consommer de crédit. Permet à l'agent IA d'estimer le coût d'une campagne avant d'appeler send_sms : 1 SMS = 160 caractères, 153 par partie au-delà. Le calcul porte sur le texte tel qu'il partira : les caractères hors alphabet SMS sont convertis automatiquement (ê en e, ç en c, € en E, guillemets et tirets typographiques en caractères simples), ceux sans équivalent sont supprimés, et { } [ ] | \ comptent double. Les émojis sont refusés par défaut (status EMOJI_NOT_ALLOWED) ; l'option émojis (Unicode, 70 caractères par SMS) s'active sur demande auprès du support SMS Vert Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Texte du SMS à analyser |
No output schema declared.
No examples provided.
generate_otp ~56
Génère et envoie un code OTP par SMS pour authentifier un utilisateur.
| Name | Type | Req | Description |
|---|---|---|---|
| sender | string | yes | Nom de l'expéditeur |
| to | string | yes | Numéro destinataire (ex: 33612345678) |
No output schema declared.
No examples provided.
get_blacklist ~25
Récupère la liste des numéros ayant envoyé STOP (liste noire).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_delivery_report ~36
Récupère le rapport de délivrabilité d'une campagne SMS.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | ID de la campagne |
No output schema declared.
No examples provided.
get_responses ~34
Récupère les réponses reçues sur une campagne SMS.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | ID de la campagne |
No output schema declared.
No examples provided.
send_sms ~185
Envoie un SMS à un ou plusieurs destinataires via SMS Vert Pro. Les numéros doivent être au format international sans le '+' (ex: 33612345678). Un SMS fait 160 caractères ; au-delà, le message part en plusieurs SMS de 153 caractères, chacun facturé (estimation avec count_sms_parts). IMPORTANT : si le compte est en route marketing, la mention 'STOP 36173' doit être ajoutée à la fin du message (obligation légale).
| Name | Type | Req | Description |
|---|---|---|---|
| delay | string | – | Envoi différé (optionnel). Format: 'YYYY-MM-DD HH:MM' |
| message | string | yes | Contenu du SMS |
| sender | string | yes | Nom de l'expéditeur (11 car. max, alphanumérique) |
| to | array | yes | Numéros au format international (ex: ['33612345678']) |
No output schema declared.
No examples provided.
verify_number ~70
Vérifie le format des numéros d'une liste de contacts (regex sur format international FR 336/337 + 11 chiffres). Retourne la liste des numéros mal formatés. Validation locale, ne consomme pas de crédits.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | ID de la liste à vérifier |
No output schema declared.
No examples provided.
verify_otp ~46
Vérifie un code OTP saisi par l'utilisateur.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Code OTP saisi |
| to | string | yes | Numéro destinataire ayant reçu le code |
No output schema declared.
No examples provided.
How do I install the SMS Vert Pro MCP server?
SMS Vert Pro is a hosted endpoint at https://www.smsvertpro.com/mcp/, 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 · www.smsvertpro.com
claude mcp add --transport http com-smsvertpro-mcp 'https://www.smsvertpro.com/mcp/'
What is the SMS Vert Pro MCP server?
SMS Vert Pro is an MCP server listed in the public MCP registry as com.smsvertpro/mcp. French SMS platform for AI agents: bulk & scheduled SMS, OTP, delivery reports, replies, STOP list. This page covers its hosted endpoint (https://www.smsvertpro.com/mcp/).
Is the SMS Vert Pro MCP server safe to use?
SMS Vert Pro scores 85 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 SMS Vert Pro MCP server expose?
SMS Vert Pro exposes 10 tools: send_sms, check_credits, get_delivery_report, get_responses, verify_number, and 5 more. Their descriptions and schemas cost roughly 725 tokens of context every time the server is loaded.
Does the SMS Vert Pro MCP server require authentication?
Yes. SMS Vert Pro asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SMS Vert Pro MCP server still maintained?
SMS Vert Pro is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.