asms
REMOTE · ASMS.AI
Phone numbers for AI agents: SMS verification codes and rented numbers that receive SMS.
Available components
Last scanned (5 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1632 tokens (~136/item across 12 items; 12 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Probed https://asms.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=asms.ai | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d35175d5e9d97b35133ff82d232e8d41 |
| SANs: asms.ai, *.asms.ai | ||||||
| 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 asms.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| asms.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://asms.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://asms.ai/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Protected resource metadata
| Document | https://asms.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://asms.ai/mcp |
| Authorisation server | https://asms.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://asms.ai/mcp | Verified | 200 | |
| http (plaintext) | http://asms.ai/mcp | HTTPS enforced | 301 | https://asms.ai/mcp |
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 →
cancel_order Cancel a verification order ~95
Rarely needed. To retry a verification do NOT cancel: just call create_otp_order again, because every unfilled order auto-refunds within 10 minutes on its own, and cancel is blocked for the first 10 minutes anyway. Only use this to release an order you are certain you no longer need once its 10-minute hold has passed.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | The orderId from create_otp_order. |
No output schema declared.
No examples provided.
cancel_rental Cancel a rental for a refund ~78
Cancel a rented number and refund it. Only possible between 5 and 120 minutes after renting, and only if the number has received no SMS; after that the rental runs to its end date.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The rented number, as rent_number or list_rentals gave it ("+", spaces and dashes are ignored). |
No output schema declared.
No examples provided.
create_otp_order Order a verification number ~240
Buy a number to receive an OTP: allocates a number, debits the wallet, and returns an orderId + phoneNumber. Then poll with poll_sms. If no code arrives, do NOT cancel to retry: simply call create_otp_order again for a fresh number and keep polling that one. Unfilled orders auto-refund within 10 minutes, so you only pay for codes that actually land and there is no penalty for ordering repeatedly. When a service keeps rejecting codes, order on the "us1" (Non-VoIP AT&T) pool, which has the highest delivery rate. WARNING: this spends real wallet balance.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Number pool to order from: "us1" = Non-VoIP AT&T (real carrier line, for strict services like WhatsApp/Telegram/Google), "us" = VoIP High Quality (lowest price, works for most signups), "uk" = United… |
| service | string | yes | Service slug to receive the OTP for (e.g. "google", "telegram", "whatsapp"). |
No output schema declared.
No examples provided.
get_balance Wallet balance ~18
Get the current wallet balance for the authenticated account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_inventory Verification number stock ~136
Get how many numbers are in stock for a service in a country. Omit `service` to list stock for every available service.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Number pool to order from: "us1" = Non-VoIP AT&T (real carrier line, for strict services like WhatsApp/Telegram/Google), "us" = VoIP High Quality (lowest price, works for most signups), "uk" = United… |
| service | string | – | Service slug to receive the OTP for (e.g. "google", "telegram", "whatsapp"). |
No output schema declared.
No examples provided.
get_pricing Verification code prices ~137
Get the retail price per OTP activation for a service in a country. Omit `service` to list prices for every available service.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Number pool to order from: "us1" = Non-VoIP AT&T (real carrier line, for strict services like WhatsApp/Telegram/Google), "us" = VoIP High Quality (lowest price, works for most signups), "uk" = United… |
| service | string | – | Service slug to receive the OTP for (e.g. "google", "telegram", "whatsapp"). |
No output schema declared.
No examples provided.
get_rental_offers Number rental prices ~233
List the rental periods and prices for a country (1 day to 12 months). A rented number is yours for the whole period and receives every SMS sent to it, unlike an OTP order, which is for one code. Omit `country` to list the countries numbers can be rented in.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country to rent a number in: "us" (United States), "uk" (United Kingdom), "ca" (Canada), "au" (Australia), "es" (Spain), "se" (Sweden), "de" (Germany), "nl" (Netherlands), "it" (Italy), "pl" (Poland)… |
No output schema declared.
No examples provided.
list_active_orders List verification orders ~45
List recent OTP orders for the account (awaiting a code or already received).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max orders to return (default 50, max 1000). |
No output schema declared.
No examples provided.
list_rentals List rented numbers ~56
List the account's rented numbers with their country, period and end date. Ended rentals are left out unless `includeEnded` is true.
| Name | Type | Req | Description |
|---|---|---|---|
| includeEnded | boolean | – | Also list rentals that have ended (default false). |
No output schema declared.
No examples provided.
poll_sms Check for the verification code ~128
Check for the SMS / OTP code on an order. Returns the code once it has arrived, otherwise an empty result: poll again after a few seconds. If nothing lands after a minute or two, the fastest path is to order a fresh number with create_otp_order (prefer the "us1" Non-VoIP pool) and leave the original: it auto-refunds within 10 minutes. Never cancel just to retry, and there is no charge for ordering again, you only pay for codes that arrive.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | The orderId from create_otp_order. |
No output schema declared.
No examples provided.
read_rental_sms Read a rented number's SMS ~65
Read the SMS a rented number has received during this rental, newest first. Poll again every few seconds while waiting for a message.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The rented number, as rent_number or list_rentals gave it ("+", spaces and dashes are ignored). |
No output schema declared.
No examples provided.
rent_number Rent a phone number ~312
Rent a phone number in a country for a period (get the periods and prices from get_rental_offers first). Debits the wallet and returns the number and when the rental ends. Read its SMS with read_rental_sms. WARNING: this spends real wallet balance; confirm the country, period and price with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country to rent a number in: "us" (United States), "uk" (United Kingdom), "ca" (Canada), "au" (Australia), "es" (Spain), "se" (Sweden), "de" (Germany), "nl" (Netherlands), "it" (Italy), "pl" (Poland)… |
| period | string | yes | Rental period: "oneDay" (1 day), "oneWeek" (1 week), "oneMonth" (1 month), "threeMonths" (3 months), "sixMonths" (6 months), "twelveMonths" (12 months). Not every period is on sale in every country:… |
No output schema declared.
No examples provided.
How do I install the asms MCP server?
asms is a hosted endpoint at https://asms.ai/mcp, 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 · asms.ai
claude mcp add --transport http ai-asms-asms 'https://asms.ai/mcp'
What is the asms MCP server?
asms is an MCP server listed in the public MCP registry as ai.asms/asms. Phone numbers for AI agents: SMS verification codes and rented numbers that receive SMS. This page covers its hosted endpoint (https://asms.ai/mcp).
Is the asms MCP server safe to use?
asms scores 82 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 asms MCP server expose?
asms exposes 12 tools: get_balance, get_pricing, get_inventory, create_otp_order, poll_sms, and 7 more. Their descriptions and schemas cost roughly 1,543 tokens of context every time the server is loaded.
Does the asms MCP server require authentication?
Yes. asms asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the asms MCP server still maintained?
asms is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.