com.jojapi/sms-verify
REMOTE · MCP.JOJAPI.COM
SMS Verify: SMS Verify API is a secure and easy-to-integrate service that sends verification codes.
Available components
Last scanned (20 hours ago)
Scores higher than 62% 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 435 tokens (~145/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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; "post_send_numeric_verify" 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
- 1 Nov 26 0
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
- 31 Oct 26 0
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
- 27 Oct 26 0
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
- 25 Oct 26 0
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
- 24 Oct 26 0
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
- 23 Oct 26 0
- Tool “post_send_numeric_verify” rewrote its description, which is the text the model reads security
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://mcp.jojapi.com/sms-verify
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.jojapi.com | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4fdef8b174aa7f510e6f8de60526c223 |
| SANs: mcp.jojapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.jojapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jojapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.jojapi.com/sms-verify | Verified | 200 | |
| http (plaintext) | http://mcp.jojapi.com/sms-verify | HTTPS enforced | 301 | https://mcp.jojapi.com/sms-verify |
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 →
get_pricing Price List ~97
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post_estimate_cost Estimate Cost ~113
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).
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON request body. |
No output schema declared.
No examples provided.
post_send_numeric_verify Send Verify SMS ~132
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 (~1464.94 avg).
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON request body. |
No output schema declared.
No examples provided.
How do I install the com.jojapi/sms-verify MCP server?
com.jojapi/sms-verify is a hosted endpoint at https://mcp.jojapi.com/sms-verify, 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 · mcp.jojapi.com
claude mcp add --transport http com-jojapi-sms-verify 'https://mcp.jojapi.com/sms-verify'
What is the com.jojapi/sms-verify MCP server?
com.jojapi/sms-verify is an MCP server listed in the public MCP registry as com.jojapi/sms-verify. SMS Verify: SMS Verify API is a secure and easy-to-integrate service that sends verification codes. This page covers its hosted endpoint (https://mcp.jojapi.com/sms-verify).
Is the com.jojapi/sms-verify MCP server safe to use?
com.jojapi/sms-verify scores 74 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 com.jojapi/sms-verify MCP server expose?
com.jojapi/sms-verify exposes 3 tools: post_send_numeric_verify, get_pricing, post_estimate_cost. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.
Does the com.jojapi/sms-verify MCP server require authentication?
No. We connected to com.jojapi/sms-verify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.jojapi/sms-verify MCP server still maintained?
com.jojapi/sms-verify 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.