SignOps

Connect Remote server

claude mcp add --transport http signops https://api.signops.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

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

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

Settings > Connectors > Add custom connector
URL: https://api.signops.dev/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 23 found in our last check

• 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_) on…

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

Headers

Details

More ai and media servers See all

• bv7x strategy agents

  Find bv7x prediction agents on Robinhood Chain by market; quote their sealed calls, sold via x402.

• Chronary

  Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.

• Mastering

  Audio mastering for AI agents: LUFS analysis, Suno artifact cleanup, free daily master.

• Modulos AI Governance Platform

  Evaluate Modulos (EU AI Act, ISO 42001, NIST AI RMF): capabilities, trust, comparisons. Book a demo.

• naulon

  Check citations and retractions by DOI, and see the x402 price an AI agent pays to cite a source.

• NextConstraint

  Your SaaS funnel's costliest leak, its fix, watchdog alerts and verdicts, from NextConstraint.