Otipi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OTIPI_KEY | No | The Otipi API key (e.g. sk_test_... or sk_live_...). This is the primary environment variable used by the server. | |
| OTIPI_API_KEY | No | Fallback environment variable for the Otipi API key, accepted if OTIPI_KEY is not set. | |
| OTIPI_BASE_URL | No | Optional base URL for the Otipi API. Defaults to https://otipi.co.il. | https://otipi.co.il |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Otipi sends SMS, email and OTP codes to Israeli numbers. Use a free test key (sk_test_, https://otipi.co.il/signup). Test mode only really delivers to numbers the account owner confirmed: add_test_recipient, ask the human for the 6-digit code, confirm_test_recipient, then send_test_otp and verify_otp. Unconfirmed numbers are sandbox only (nothing arrives). Phone format: +9725XXXXXXXX. get_integration_snippet returns Next.js, Supabase and Express code and needs no key.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_test_otpA | Send a one-time verification code (OTP) by SMS or email to a phone number in Israel using Otipi, in test mode. Use this to try the login/2FA flow end to end. With a test key the message really arrives ONLY if the recipient was confirmed with add_test_recipient + confirm_test_recipient; otherwise it is kept in the sandbox log and nothing is delivered. The result says which case happened and includes test_code when available, so you can verify it with verify_otp. Each account has 5 free test SMS for life. |
| verify_otpA | Check a one-time code that was sent with send_test_otp (or the live API) for a phone number or email. Returns valid true/false and, when false, the reason (wrong_code, expired_or_missing, too_many_attempts). |
| add_test_recipientA | Start confirming a phone number or email as a test recipient. A 6-digit code is sent to it. Once confirmed, test messages to that recipient really arrive (otherwise test mode only logs them in a sandbox). Only add numbers or emails that belong to the account owner. Test key (sk_test_) only. After calling this, ask the human for the 6-digit code they received and call confirm_test_recipient. |
| confirm_test_recipientA | Finish confirming a test recipient with the 6-digit code the human received after add_test_recipient. On success, send_test_otp to this recipient is really delivered. |
| list_test_recipientsA | List the confirmed and pending test recipients of this account and how many of the 5 free test SMS are left. Call it before send_test_otp to know whether a number will really receive messages. |
| check_delivery_statusA | Look up a sent message by message_id (returned by send_test_otp) and report its status (queued, sent, delivered, opened, failed, bounced), whether test delivery was real or sandbox, and the event timeline. |
| get_integration_snippetA | Return ready-to-paste code for adding Otipi phone/OTP login to a project: Next.js App Router (API routes plus a client component), Supabase Auth (Send SMS hook setup plus client code) or Express. Works offline and does not need an API key. Use it when the user wants to integrate SMS verification or 2FA for Israeli numbers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct role: sending vs verifying OTPs, recipient onboarding (add/confirm/list), delivery lookup, and code snippet retrieval. The only mild friction is that verify_otp and confirm_test_recipient both 'check a code', but the descriptions clearly separate end-user OTP verification from test-recipient confirmation.
All names are snake_case and verb-first (verify_, send_, add_, confirm_, list_, check_, get_) with clear object nouns. The multi-word object forms (test_otp, test_recipient, delivery_status, integration_snippet) are used consistently.
Seven tools is well-scoped for a test-mode OTP/integration workflow, with each tool earning its place across recipient setup, sending, verifying, status, and code snippets. No redundant or filler tools.
The surface covers the full test flow: recipient creation/confirmation/listing, OTP send and verify, delivery status, and integration snippets. Minor gaps exist — no way to remove or revoke a test recipient and no live-mode send tool — but agents can work around these.