Is the Envoisms MCP server down?

mcp-registry/ma.envoisms/envoisms · v1.0.0

As of 2026-10-22 12:02 UTC, the Envoisms MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

Send SMS/WhatsApp and verify OTP codes in Morocco (+212) and worldwide. Direct carrier routing.

claude mcp add --transport http envoisms-mcp-server https://api.envoisms.ma/v1/mcp

{
  "mcpServers": {
    "envoisms-mcp-server": {
      "type": "http",
      "url": "https://api.envoisms.ma/v1/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

What to fix (6)

Auto-fix: 14 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fma.envoisms%2Fenvoisms/fixes

{
  "name": "create_topup",
  "description": "Create a balance top-up checkout link (Stripe card or crypto USDC) for the authenticated account.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "pack_id": {
        "type": "string",
        "description": "SMS top-up pack ID (e.g. 'sms-300' for 300 MAD, 'sms-1000' for 1000 MAD, 'sms-5000' for 5000 MAD). Optional if amount_mad is provided."
      },
      "currency": {
        "enum": [
          "mad",
          "eur"
        ],
        "type": "string",
        "description": "Payment presentation currency for card checkout ('mad' or 'eur'). Default 'mad'."
      },
      "amount_mad": {
        "type": "number",
        "description": "Custom recharge amount in MAD (minimum 300 MAD). Optional if pack_id is provided."
      },
      "payment_method": {
        "enum": [
          "stripe",
          "crypto"
        ],
        "type": "string",
        "description": "Payment method ('stripe' for card or 'crypto' for USDC). Default 'stripe'."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "get_analytics",
  "description": "Get SMS & WhatsApp message delivery metrics, success rates, and volume statistics.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "days": {
        "type": "number",
        "description": "Lookback window in days (1-365, default 30)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_balance",
  "description": "Check remaining SMS credit balance in MAD and account status.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ma.envoisms/envoisms"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ma.envoisms/envoisms"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~2,038 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.

Largest tool definitions

• send_whatsapp_template ~265 tokens
• create_topup ~220 tokens
• send_bulk_sms ~139 tokens
• list_messages ~138 tokens
• list_sender_ids ~120 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fma.envoisms%2Fenvoisms.svg)](https://glimind.com/server/mcp-registry%2Fma.envoisms%2Fenvoisms?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fma.envoisms%2Fenvoisms?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fma.envoisms%2Fenvoisms.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fma.envoisms%2Fenvoisms.svg
   :target: https://glimind.com/server/mcp-registry%2Fma.envoisms%2Fenvoisms?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8bc35b9736b622fc…, first seen 2026-10-17, included at leaf 4199 of 45,819. Version history · verify what your client received.

Tools (18)

• create_topup
• get_analytics
• get_balance
• get_message_status
• get_pricing
• list_campaigns
• list_contacts
• list_messages
• list_sender_ids
• lookup_number
• ops_monitoring
• ops_pulse
• ops_route_quality
• send_bulk_sms
• send_otp
• send_sms
• send_whatsapp_template
• verify_otp

Compare: most reliable payments servers · most reliable analytics servers · most reliable communication servers · most reliable data servers · most reliable devops servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Envoisms MCP server down right now?

As of 2026-10-22 12:02 UTC, the Envoisms MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

How many tools does Envoisms MCP server provide?

Envoisms MCP server advertises 18 tools, including create_topup, get_analytics, get_balance, get_message_status, get_pricing.

How do I install Envoisms MCP server?

Point your MCP client at this streamable-http endpoint: https://api.envoisms.ma/v1/mcp

Is the Envoisms MCP server safe to connect to an AI agent?

Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Envoisms MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.