SignOps

dev.signopsPublished by signops.devOfficial publisherv1.0.0Updated Oct 27, 2026

Send push to Android, iOS and the web, and ask a trusted phone to approve a login, from your agent.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

SignOps lets an assistant send push notifications to Android, iOS and web users, manage devices and templates, and request login approvals, passkeys and…

What you can do
  • Send, inspect, list and cancel push notifications to one user, a list, a topic or everyone
  • Register, list and remove devices, and manage topic subscriptions
  • Create, read, save and delete push templates with placeholder fields
  • Request, check and cancel phone-based approval requests with number matching
  • Inspect passkeys, authenticator app status, unlock locked users and remove authenticators
  • Read consent answers and export everything held on one user as JSON
When to use it
Useful when an assistant should notify app users, run a human approval step for a login or sensitive action, or look up a user's devices, passkeys, authenticator state and consent from a SignOps account.
Requirements
A remote streamable HTTP endpoint at api.signops.dev; no local package. Requires a SignOps secret key sent as a bearer token in the Authorization header, and an app with users and devices registered through the SignOps SDK.
Before you install
The key decides the mode: a live key reaches real users, so prefer a test key while building. Sending pushes, registering or removing devices, changing topics and templates, creating approvals, removing authenticators and unlocking users all change real data. Export returns personal data including device tokens, passkeys, approvals and consent history.

Installation

In SourceWeft

  1. Open SignOps in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.signops%2Fsignops/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "signops": {
      "type": "http",
      "url": "https://api.signops.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

23

send_push

Send a push

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.

Parametersallbodydatalinkimagetitletopicfieldssend_atuser_idtemplateuser_ids+3 more

get_push

Get a push

One push by id: status, devices, sent and failed, per platform.

Parametersidrequired

list_pushes

List pushes

Pushes, newest first. On the Free plan only pushes still to go are listed (no delivery logs).

Parameterslimitbefore

cancel_push

Cancel a scheduled push

Cancel a push that is scheduled and has not started sending.

Parametersidrequired

register_device

Register a device

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.

Parametersnametokenrequireduser_idrequiredplatformrequired

list_devices

List a user's devices

The devices registered for one user id, newest first, with platform and whether each is trusted for approvals.

Parametersuser_idrequired

remove_device

Remove a device

Remove one device by id; it gets no more pushes.

Parametersidrequired

list_topics

List topics

Topics with how many users each has.

Takes no parameters.

subscribe_topic

Subscribe a user to a topic

Add a user to a topic. The topic exists once it has a user.

Parameterstopicrequireduser_idrequired

unsubscribe_topic

Unsubscribe a user from a topic

Take a user off a topic.

Parameterstopicrequireduser_idrequired

list_templates

List templates

Saved push templates with their fields.

Takes no parameters.

get_template

Get a template

One template by name.

Parametersnamerequired

save_template

Save a template

Create or replace a template. Put {{field}} where a value goes, or {{field|default}} for one with a fallback.

Parametersbodydatalinknamerequiredimagetitle

delete_template

Delete a template

Delete a template by name. Pushes already made from it are not changed.

Parametersnamerequired

create_approval

Ask a user to approve

Send an approval request to the user's trusted phone, with number matching. The user must have a phone enrolled through the SignOps SDK.

Parameterscontextrequireduser_idrequired

get_approval

Get an approval

An approval request's status: pending, approved, denied, expired or cancelled.

Parametersidrequired

cancel_approval

Cancel an approval

Cancel a pending approval request.

Parametersidrequired

list_passkeys

List a user's passkeys

The passkeys registered for one user id.

Parametersuser_idrequired

get_authenticator

Get a user's authenticator

Whether a user has an authenticator app (TOTP) confirmed, when it was last used, backup codes left, and whether wrong codes have locked them.

Parametersuser_idrequired

remove_authenticator

Remove a user's authenticator

Remove a user's authenticator app and backup codes, for a lost phone. They can enrol again.

Parametersuser_idrequired

unlock_user

Unlock a user

Clear the lock that five wrong codes in 15 minutes put on a user, and their count of wrong codes.

Parametersuser_idrequired

export_user

Export a user's data

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.

Parametersuser_idrequired

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.