MyOTP.App MCP integration for AI agents.
Connect AI agents to MyOTP.App through 5 structured actions, including check otp status, extend otp, and generate otp. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the MyOTP.App integration exposes
The MyOTP.App Agent App exposes 5 provider-backed actions for security and communication work. Its current contract lets an authorized agent check the delivery and validity status of a myotp.app otp message, extend the expiry time of an existing myotp.app otp, and generate and deliver an otp through myotp.app by sms or whatsapp. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected MyOTP.App account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real MyOTP.App capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_otp_statusREADCheck the delivery and validity status of a MyOTP.App OTP message.
INPUTS: message_id
extend_otpREVIEWExtend the expiry time of an existing MyOTP.App OTP.
INPUTS: message_id / duration
generate_otpREVIEWGenerate and deliver an OTP through MyOTP.App by SMS or WhatsApp.
INPUTS: phone_number / otp_length / otp_validity / channel / template_order
get_transactions_reportREADRetrieve a paginated MyOTP.App transaction report for a date range.
INPUTS: start_date / end_date / page / per_page
verify_otpREVIEWVerify an OTP using its message id or destination phone number.
INPUTS: otp / message_id / phone_number
INPUT CONTRACTS
Know what the action needs before it runs.
check_otp_status
message_idOPTIONAL- The message identifier of the OTP to inspect.
extend_otp
message_idOPTIONAL- The message identifier of the OTP to extend.
durationOPTIONAL- The number of seconds to add to the OTP expiry time.
generate_otp
phone_numberREQUIRED- The E.164 phone number including country code without a prefix.
otp_lengthOPTIONAL- The number of digits in the generated OTP.
otp_validityOPTIONAL- The OTP validity period in seconds.
channelOPTIONAL- The channel used to deliver the OTP.
template_orderOPTIONAL- The configured message template order.
get_transactions_report
start_dateOPTIONAL- The first report date in YYYY-MM-DD format.
end_dateOPTIONAL- The last report date in YYYY-MM-DD format.
pageOPTIONAL- The one-based report page number.
per_pageOPTIONAL- The maximum number of transactions to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Otp Status
Check the delivery and validity status of a MyOTP.App OTP message. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_otp_statusVerify with Get Transactions Report
Retrieve a paginated MyOTP.App transaction report for a date range. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_transactions_reportSAFETY BOUNDARY
Operate MyOTP.App with explicit limits
- Authorize MyOTP.App with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned MyOTP.App data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in MyOTP.App rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the MyOTP.App task completed successfully.
CONNECTION MODEL
API key
MyOTP.App API key from https://myotp.app/dashboard/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by MyOTP.App.