Send push to Android, iOS and the web, and ask a trusted phone to approve a login, from your agent.
Scored across 23 tools
Most tools map cleanly to a distinct resource+action (cancel_approval vs cancel_push, get_push vs list_pushes, get_template vs list_templates), so misselection is unlikely. The only mild overlap is in the identity area, where get_authenticator, remove_authenticator, and unlock_user all touch similar user state but still describe separable actions.
Nearly every tool follows a consistent verb_noun snake_case pattern (send_push, list_devices, create_approval, remove_device, subscribe_topic). Exceptions like export_user and unlock_user still fit the pattern, and save_template is the only slight deviation (create-or-replace).
23 tools is on the heavy side but justified by the breadth of the domain: pushes, templates, devices, topics, approvals, passkeys, authenticator, and consent. Roughly three tools per sub-area means each tool earns its place, though it sits just below the 'heavy' threshold.
Push lifecycle (send/cancel/list/get), template management (save/get/list/delete), device management (register/remove/list), topics, approvals, and authenticator handled well. Minor gaps exist: passkeys are read-only (no register/remove via this surface), consent is read-only, and there is no explicit topic deletion, but these are likely SDK-side and can be worked around.
Cancel a pending approval request.
Inputs: id (required).
Cancel a push that is scheduled and has not started sending.
Inputs: id (required).
Send an approval request to the user's trusted phone, with number matching. The user must have a phone enrolled through the SignOps SDK.
Inputs: context (required), user_id (required).
Delete a template by name. Pushes already made from it are not changed.
Inputs: name (required).
Everything SignOps holds on one user id as JSON: devices (tokens shortened), topics, passkeys, authenticator status, approvals of the last 90 days, consent history and pushes sent to them.
Inputs: user_id (required).
An approval request's status: pending, approved, denied, expired or cancelled.
Inputs: id (required).
Whether a user has an authenticator app (TOTP) confirmed, when it was last used, backup codes left, and whether wrong codes have locked them.
Inputs: user_id (required).
The latest consent answer per purpose for one user, like marketing_push, and the history.
Inputs: user_id (required).
One push by id: status, devices, sent and failed, per platform.
Inputs: id (required).
One template by name.
Inputs: name (required).
The devices registered for one user id, newest first, with platform and whether each is trusted for approvals.
Inputs: user_id (required).
The passkeys registered for one user id.
Inputs: user_id (required).
Pushes, newest first. On the Free plan only pushes still to go are listed (no delivery logs).
Inputs: limit, before.
Saved push templates with their fields.
Inputs: no named parameters.
Topics with how many users each has.
Inputs: no named parameters.
Store a device's push token under your user id. Android and iOS tokens come from the Firebase or Apple SDK; for web, token is the PushSubscription as JSON.
Inputs: token (required), user_id (required), platform (required), name.
Remove a user's authenticator app and backup codes, for a lost phone. They can enrol again.
Inputs: user_id (required).
Remove one device by id; it gets no more pushes.
Inputs: id (required).
Create or replace a template. Put {{field}} where a value goes, or {{field|default}} for one with a fallback.
Inputs: name (required), body, data, link, +2 more.
Send a push notification to one user (user_id), a list (user_ids, up to 1,000), a topic, or everyone (all: true). Give exactly one target. A push to one user, sent now, answers with its result at once; others answer with status sending or scheduled. With a test key (sk_test_) only test devices receive it.
Inputs: all, body, data, link, +11 more.
Add a user to a topic. The topic exists once it has a user.
Inputs: topic (required), user_id (required).
Clear the lock that five wrong codes in 15 minutes put on a user, and their count of wrong codes.
Inputs: user_id (required).
Take a user off a topic.
Inputs: topic (required), user_id (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Let agents send content-free push notifications to a paired phone via MCP.
Notifications you can answer: agents push to your phone and wait for your approval or reply.
Poke your human for approvals and decisions during agent sessions — answered with one phone tap.
Reach your own phone from an AI agent: notifications, approval questions, reminders, ring, files.
Add one secure layer between your agents and this server.
