sms-verify MCP server
com.jojapi/sms-verifyjojapi.comstreamable-httpv1.0.0Scanned
SMS Verify: SMS Verify API is a secure and easy-to-integrate service that sends verification codes.
3 tools: 1 do something that can't be undone, 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the sms-verify MCP server can do
The sms-verify MCP server is published by jojapi.com, a domain the MCP Registry verified. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (post_send_numeric_verify) and create or change data (1 tool: post_estimate_cost), but cannot delete data. 1 tool only reads.
2 tools can send data out of your system (post_send_numeric_verify and post_estimate_cost).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Can't be undone 1Claude Code: ask
post_send_numeric_verifySends 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.Can send data outNo findings
Why it is in this group
- The name "post_send_numeric_verify" says "post": a word for a change.
- The name "post_send_numeric_verify" also says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "post_send_numeric_verify" says "post": it sends or publishes something to other people.
Description, as the server wrote it 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 (~1026.96 avg).
Changes things 1Claude Code: ask
post_estimate_costWhat 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 rang…Can send data outNo findings
Why it is in this group
- The name "post_estimate_cost" says "post": a word for a change.
What it can reach
- outboundThe name "post_estimate_cost" says "post": it sends or publishes something to other people.
Description, as the server wrote it 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.6 avg).
Only reads 1Show 1 read-only tool
get_pricingWhat a verification SMS costs in every country it can be sent to, in credits, sorted by country name.No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote 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 (~0.64 avg).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.jojapi.com/sms-verify: tools/list returned 3 tools to an anonymous client, including post_send_numeric_verify (irreversible), post_estimate_cost (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:get_pricingOnly readsdescription
- Changed:post_estimate_costChanges thingsdescription
- Changed:post_send_numeric_verifyCan't be undonedescription
Tools1 changed.~1 changedView diff
- Changed:post_send_numeric_verifyCan't be undonedescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http sms-verify https://mcp.jojapi.com/sms-verifyclaude mcp add --transport http sms-verify https://mcp.jojapi.com/sms-verifyRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__sms-verify__get_pricing"
],
"ask": [
"mcp__sms-verify__post_send_numeric_verify",
"mcp__sms-verify__post_estimate_cost"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sms-verify. Review it before you use it.
Capability tags behind 2 rules
- mcp__sms-verify__post_send_numeric_verify outbound
- mcp__sms-verify__post_estimate_cost outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.jojapi/sms-verify/verify?hash=2f0cfeeaaf9343e5af0b87a11722eea1ba4374ad02abc08f8d584d5d5728f755" | jq -e '.changed == false'Pinned hash 2f0cfeeaaf93, from Nov 18, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.jojapi/sms-verify/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.jojapi/sms-verify)Source: MCP Registry. Synced Oct 21, 2026, 17:57 UTC.
sms-verify MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the sms-verify MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the sms-verify MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the sms-verify MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: post_send_numeric_verify.
What tools does the sms-verify MCP server have?
- 3 tools: 1 irreversible, 1 write, 1 read. post_send_numeric_verify, post_estimate_cost and get_pricing.
Does the sms-verify MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the sms-verify MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): post_send_numeric_verify and post_estimate_cost.
Has the sms-verify MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.