com.jojapi/sms-verify is an MCP server published by com.jojapi, hosted at mcp.jojapi.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 3 tools, including post_send_numeric_verify, get_pricing, post_estimate_cost.
SMS Verify: SMS Verify API is a secure and easy-to-integrate service that sends verification codes.
144 connections through 4 shared values. Tap any node.
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 (~1072.73 avg).
| Parameter | Type | Description |
|---|---|---|
| body | object | JSON request body. |
{
"name": "post_send_numeric_verify",
"title": "Send Verify SMS",
"description": "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 (~1072.73 avg).",
"inputSchema": {
"type": "object",
"properties": {
"body": {
"type": "object",
"required": [
"target"
],
"properties": {
"target": {
"type": "string",
"example": "+1 201 555 0123",
"description": "The phone number in international format, with its country calling code, for example `+1 201 555 0123`. Spaces and dashes are allowed; a missing `+` is added."
}
},
"description": "JSON request body."
}
},
"additionalProperties": false
}
}Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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 (~1 avg).
No parameters.
{
"name": "get_pricing",
"title": "Price List",
"description": "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 (~1 avg).",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
}
}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.91 avg).
| Parameter | Type | Description |
|---|---|---|
| body | object | JSON request body. |
{
"name": "post_estimate_cost",
"title": "Estimate Cost",
"description": "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.91 avg).",
"inputSchema": {
"type": "object",
"properties": {
"body": {
"type": "object",
"required": [
"target"
],
"properties": {
"target": {
"type": "string",
"example": "+1 201 555 0123",
"description": "The phone number in international format, with its country calling code, for example `+1 201 555 0123`. Spaces and dashes are allowed; a missing `+` is added."
}
},
"description": "JSON request body."
}
},
"additionalProperties": false
}
}Tools are the documented endpoints of SMS Verify on the JoJ API marketplace, called through the live gateway. Calls require a JoJ API key sent as an HTTP header on this MCP connection (Authorization: Bearer jk_...). Keys: https://jojapi.com/workspace/api-keys · Plans: https://jojapi.com/hub/api/sms-verify/pricing · Docs: https://jojapi.com/hub/api/sms-verify
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.