Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ucode SMS

REMOTE · MCP.UCODESIM.COM

Virtual phone numbers for SMS/OTP verification. Browse free; pay with credits or USDC (x402).

Available components

−55 this week 23 Trust /100

Last scanned (17 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Recent critical change

Authorization (3 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 15 Nov 26 −55
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 +55
    • Authorization: unverified → fail ▼ critical
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 24 Oct 26 −55
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.ucodesim.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ucodesim.com CN=YE2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 68f46e61b46490ad583a36cb51791628192
SANs: *.ucodesim.com, ucodesim.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.ucodesim.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
ucodesim.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 502
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.ucodesim.com/mcp HTTP error 502
http (plaintext) http://mcp.ucodesim.com/mcp HTTPS enforced 301 https://mcp.ucodesim.com/mcp
MCP tools · 50 exposed · ~3,445 tokens

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 →

Tool Tokens
ucode_sign_out ~40

Same as **ucode_disconnect** — unlinks Ucode from this ChatGPT chat. Call for sign out, log out, or disconnect requests.

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_active_rentals ~24

Active/received rentals with SMS snippets if already fetched.

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_cancel_rental ~88

Cancel an active rental and refund credits when no SMS has arrived. Requires a cancel reason for analytics. Reasons: service_rejected | number_has_account | code_not_arrived | other. If an SMS arrives during cancel, credits stay charged and the code is returned.

NameTypeReqDescription
reasonstringyes–
reasonNotestring––
rentalIdstringyes–
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_countries ~50

Raw worldwide country id table — pairs with legacy APIs only. For renting, use **ucode_sms_summary** / **ucode_sms_service_detail** so users pick by country name + credits.

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_get_code ~32

Poll latest SMS for a rental id (provider rental id string).

NameTypeReqDescription
rentalIdstringyes–
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_prices ~81

**Avoid for ChatGPT users.** Uses backend USD-ish snapshots; assistants must guide rentals via credits-only summaries (**ucode_sms_summary**, **ucode_sms_service_detail**) and **ucode_sms_rent_packages**. Responses are partially sanitized.

NameTypeReqDescription
countrynumber––
minutesnumber––
servicestring––
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_refund_expired ~26

Trigger server-side refund scan for expired rentals (same as app).

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_rent_packages ~83

After user picks **serviceCode** + **country** (numeric id from summary/detail), list **credit-priced routes** only. Same package picker as the app (rentalFlowVersion 2). Present **credits**, recommended badge, labels — never quote USD or backend provider names.

NameTypeReqDescription
countrynumberyes–
servicestringyes–
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_rent_provider_direct ~68

**Do not use for ChatGPT end users.** Legacy rental against upstream balances — skips normal credit UX and exposes provider-era assumptions. Only **ucode_sms_rent_with_credits** with packages.

NameTypeReqDescription
countrynumber––
servicestringyes–
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_rent_with_credits ~114

**Primary rental** — charges Ucode credits. Always use **rentalFlowVersion: 2** and **packageId** from **ucode_sms_rent_packages** (matches mobile). Never mention wholesale/provider IDs or dollar amounts to the user.

NameTypeReqDescription
clientCreditsnumber––
countrynumberyes–
packageIdstring––
rentalFlowVersion––Use **2** (default flow); matches mobile package picker.
servicestringyes–
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_service_detail ~85

Load one service’s countries after you have its short **serviceCode** (from summary `service` field). Matches opening that service in the iOS/Android app: availability, credits per country. Prefer over legacy `/prices` APIs.

NameTypeReqDescription
serviceCodestringyesShort code, e.g. tg, wa, fb — same as mobile app service id
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_services ~47

Low-level provider service codes — exposes internal naming. Do NOT use for normal rentals; prefer **ucode_sms_summary** or **ucode_sms_service_detail** then credits-only packages.

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_summary ~124

Primary discovery: search by app/service name (e.g. Telegram, WhatsApp). Returns services with countries, **credits** only (no provider names / no USD in assistant copy). Same idea as the app Services tab. Then **ucode_sms_service_detail** or go straight to **ucode_sms_rent_packages** once service + country are chosen.

NameTypeReqDescription
limitnumber––
pagenumber––
searchstring––
sortBystring––
sortOrderstring––
v–––
NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_sms_transactions ~36

Provider ledger audit trail — sanitized before ChatGPT. Prefer explaining rentals via **ucode_sms_active_rentals** for users.

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_welcome ~37

Same as **ucode_render_home** — product summary + sign-in card. Prefer **ucode_render_home** on first message.

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

ucode_whoami ~29

Current linked Ucode user (requires ucode_login_poll complete or ucode_authenticate).

Input schema present but exposes no named parameters.

NameTypeReqDescription
billingUrlstring––
codestring––
countryNamestring––
creditsnumber––
dataobject––
endDatestring––
errorstring––
httpStatusnumber––
neededCreditsnumber––
okbooleanyes–
phonestring––
phoneNumberstring––
providerRentalIdstring––
remainingSecondsnumber––
rentalIdstring––
serviceNamestring––
smsCodestring––
summarystringyes–
uiViewstring––

No examples provided.

Install

How do I install the Ucode SMS MCP server?

Ucode SMS is a hosted endpoint at https://mcp.ucodesim.com/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 · mcp.ucodesim.com

# add to Claude Code
claude mcp add --transport http uk-ucode-sms 'https://mcp.ucodesim.com/mcp'
Common questions

What is the Ucode SMS MCP server?

Ucode SMS is an MCP server listed in the public MCP registry as uk.ucode/sms. Virtual phone numbers for SMS/OTP verification. Browse free; pay with credits or USDC (x402). This page covers its hosted endpoint (https://mcp.ucodesim.com/mcp).

Is the Ucode SMS MCP server safe to use?

Ucode SMS scores 23 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 Ucode SMS MCP server expose?

Ucode SMS exposes 50 tools: ucode_render_home, ucode_render_services, ucode_welcome, ucode_session_status, ucode_panel_ping, and 45 more. Their descriptions and schemas cost roughly 3,445 tokens of context every time the server is loaded.

Does the Ucode SMS MCP server require authentication?

Its publisher declares no required credentials for Ucode SMS. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Ucode SMS MCP server still maintained?

Ucode SMS is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Ucode SMS MCP server?

VerifyMCP ran 5 checks on Ucode SMS, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Ucode SMS: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.