Sms Verify

com.jojapiPublished by jojapi.comOfficial publisherv1.0.0Updated Oct 24, 2026

SMS Verify: SMS Verify API is a secure and easy-to-integrate service that sends verification codes.

The publisher's own server: Ahrefs

VerifiedStreamable HTTPWeb executableFinanceCommunication & Collaboration

Overview

AI-generated overview

Sends six-digit SMS verification codes to phone numbers and reports per-country and per-number credit costs.

What you can do
Send a six-digit verification code by SMS to a phone number and get the code back to compare with what the user types, charged in credits per message sent to the destination country or carrier.
When to use it
Use it when an assistant needs to verify that a user controls a phone number through an SMS one-time code, or to check what such a message would cost before sending it.
Requirements
A remote MCP endpoint; no local runtime, account or key is declared in the listing. Sending messages consumes credits, so a funded balance is implied.
Before you install
Sending a code spends credits equal to the message cost, which varies by destination country and carrier. Messages go to third-party mobile networks, and the tool returns the code itself, so handle it as sensitive.

Installation

In SourceWeft

  1. Open Sms Verify in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.jojapi%2Fsms-verify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sms-verify": {
      "type": "http",
      "url": "https://mcp.jojapi.com/sms-verify"
    }
  }
}

Tools

3

post_send_numeric_verify

Send Verify SMS

Sends a six-digit verification code to a phone number by SMS and returns the code, so you can compare it with what the user types. The message reads `123-456 is your verification code. Don't share.` The request is charged the message's cost in credits (`cost`), which depends on the destination country and carrier; a message that would cost more than 10,000 credits is not sent (`max_cost_exceeded`). Failed requests are not charged. Group: Verification. Billing per call: Credits: metered (~398.67 avg).

Parametersbody

get_pricing

Price List

What a verification SMS costs in every country it can be sent to, in credits, sorted by country name. Each country is priced for a typical mobile number and checked at least once a day (`checked_at`, UTC); carriers within a country can differ, so use Estimate Cost for an exact number. Countries SMS cannot be sent to are left out. Group: Pricing. Billing per call: Requests: metered (~0.41 avg).

Takes no parameters.

post_estimate_cost

Estimate Cost

What a verification SMS to this phone number would cost, in credits, and the number's country (`region_code`, ISO 3166-1 alpha-2; `null` when the number belongs to no assigned range). Nothing is sent. The price is for this number's carrier, so it can differ from the country's price in the price list. Group: Pricing. Billing per call: 0 Credits, Requests: metered (~0.36 avg).

Parametersbody

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Jojapi integrations