SignOps

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Developer tools
• You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

claude mcp add --transport http signops https://api.signops.dev/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "signops": {
      "url": "https://api.signops.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "signops": {
      "type": "http",
      "url": "https://api.signops.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• Authorization secret required HTTP header
  Bearer and your SignOps secret key. Use a test key (sk_test_) while building.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• send_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_) onl

• get_push

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

• list_pushes

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

• cancel_push

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

• register_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.

• list_devices

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

• remove_device

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

• list_topics

  Topics with how many users each has.

• subscribe_topic

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

• unsubscribe_topic

  Take a user off a topic.

• list_templates

  Saved push templates with their fields.

• get_template

  One template by name.

• save_template

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

• delete_template

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

• create_approval

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

• get_approval

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

• cancel_approval

  Cancel a pending approval request.

• list_passkeys

  The passkeys registered for one user id.

• get_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.

• remove_authenticator

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

• unlock_user

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

• export_user

  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.

• get_consent

  The latest consent answer per purpose for one user, like marketing_push, and the history.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

• ! Caution

  Maker matches the repo

  The registry lists no source repo, so we cannot match the publisher (signops.dev) to the code

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 161 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 23 tool descriptions and found no hidden instructions to the AI

Compared with others in Developer toolsi

• More stars than 0% of the other 4924 servers in this category
• Published to the registry more recently than 73% of the other 4924 servers in this category
• Basic checks equal to or better than 24% of the other 4924 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo