SMS.ir MCP Server

Created By
kazemsofta year ago
MCP Server for SMS.ir messaging services
Overview

What is SMS.ir MCP Server?

The SMS.ir MCP Server is a Model Context Protocol (MCP) server designed for SMS.ir messaging services, enabling AI assistants to send SMS messages via the SMS.ir API.

How to use SMS.ir MCP Server?

To use the SMS.ir MCP Server, you can install it via npm using npx or manually clone the repository and set it up. You will need an API key from SMS.ir to configure the server.

Key features of SMS.ir MCP Server?

  • Send single SMS messages to individual recipients.
  • Send bulk SMS messages to multiple recipients.
  • Send verification code SMS messages using templates.
  • Check account credit balance.

Use cases of SMS.ir MCP Server?

  1. Sending notifications or alerts via SMS.
  2. Implementing two-factor authentication through verification codes.
  3. Bulk messaging for marketing campaigns.

FAQ from SMS.ir MCP Server?

  • How do I get an API key from SMS.ir?

Create an account on SMS.ir, log in, and generate your API key from the user panel.

  • Can I send bulk SMS messages?

Yes, the server supports sending bulk SMS messages to multiple recipients.

  • Is there a way to check my account credit?

Yes, you can check your remaining credit balance using the provided API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kazemsoft
Star
0
Language
JavaScript
License
MIT license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago