# SignOps (remote · api.signops.dev)

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

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.signops.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-signops-signops/api.md), [page](https://verifymcp.io/servers/dev-signops-signops/api)

## Channel facts

- Endpoint: `https://api.signops.dev/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1467 tokens (~63/item across 23 items; 23 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SignOps MCP server?

SignOps is a hosted endpoint at https://api.signops.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-signops-signops 'https://api.signops.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-signops-signops": {
      "url": "https://api.signops.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-signops-signops": {
      "type": "http",
      "url": "https://api.signops.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-signops-signops]
url = "https://api.signops.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-signops-signops": {
      "type": "remote",
      "url": "https://api.signops.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-signops-signops --url 'https://api.signops.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-signops-signops:
    url: "https://api.signops.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-signops-signops": {
      "Transport": "http",
      "Url": "https://api.signops.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-signops-signops -t streamable-http -u 'https://api.signops.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-signops-signops": {
      "type": "http",
      "url": "https://api.signops.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 69, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 96
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-10-25 (score 28)

First indexed and scored.

## MCP tools (23)

### `send_push` (~360 tokens)

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.

Input parameters:

- `all` (boolean): true to send to every device of the app.
- `body` (string): The text under it.
- `data` (object): Key and value pairs the app reads. With no title, the push is silent.
- `fields` (object): Values for the template's {{fields}}.
- `fields_by_user` (object): With user_ids: each user's own field values, keyed by user id.
- `idempotency_key` (string): Optional. The same key within 24 hours replays the first answer instead of sending again.
- `image` (string): An https image URL.
- `link` (string): A deep link or URL opened on tap.
- `marketing` (boolean): true applies the app's daily cap of marketing pushes per user.
- `send_at` (string): An ISO time with a zone, up to 30 days ahead, like 2026-10-24T18:00:00+05:30.
- `template` (string): A saved template's name; title, body and the rest come from it.
- `title` (string): The notification title.
- `topic` (string): A topic name.
- `user_id` (string): Your own id for one user.
- `user_ids` (array): Up to 1,000 of your user ids.

### `get_push` (~37 tokens)

Get a push

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

Input parameters:

- `id` (string, required): The push id, msg_...

### `list_pushes` (~52 tokens)

List pushes

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

Input parameters:

- `before` (string): The next value from the previous page.
- `limit` (integer)

### `cancel_push` (~33 tokens)

Cancel a scheduled push

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

Input parameters:

- `id` (string, required): The push id, msg_...

### `register_device` (~90 tokens)

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.

Input parameters:

- `name` (string): Optional label, like Rushi's iPhone.
- `platform` (string, required)
- `token` (string, required): The push token.
- `user_id` (string, required): Your own id for the user.

### `list_devices` (~43 tokens)

List a user's devices

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

Input parameters:

- `user_id` (string, required): Your own id for the user.

### `remove_device` (~33 tokens)

Remove a device

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

Input parameters:

- `id` (string, required): The device id, dev_...

### `list_topics` (~16 tokens)

List topics

Topics with how many users each has.

### `subscribe_topic` (~59 tokens)

Subscribe a user to a topic

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

Input parameters:

- `topic` (string, required): Up to 64 letters, digits, dashes, dots or underscores.
- `user_id` (string, required): Your own id for the user.

### `unsubscribe_topic` (~39 tokens)

Unsubscribe a user from a topic

Take a user off a topic.

Input parameters:

- `topic` (string, required): The topic name.
- `user_id` (string, required): Your own id for the user.

### `list_templates` (~15 tokens)

List templates

Saved push templates with their fields.

### `get_template` (~27 tokens)

Get a template

One template by name.

Input parameters:

- `name` (string, required): The template name, like payment_received.

### `save_template` (~111 tokens)

Save a template

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

Input parameters:

- `body` (string): Body, with {{fields}}.
- `data` (object): Optional data, with {{fields}} in the values.
- `image` (string): Optional image URL.
- `link` (string): Optional link.
- `name` (string, required): Lowercase letters, digits and underscores.
- `title` (string): Title, with {{fields}}.

### `delete_template` (~34 tokens)

Delete a template

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

Input parameters:

- `name` (string, required): The template name.

### `create_approval` (~75 tokens)

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.

Input parameters:

- `context` (string, required): What they are approving, up to 120 characters, like Sign in from Chrome on Windows.
- `user_id` (string, required): Your own id for the user.

### `get_approval` (~38 tokens)

Get an approval

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

Input parameters:

- `id` (string, required): The approval id, apr_...

### `cancel_approval` (~28 tokens)

Cancel an approval

Cancel a pending approval request.

Input parameters:

- `id` (string, required): The approval id, apr_...

### `list_passkeys` (~32 tokens)

List a user's passkeys

The passkeys registered for one user id.

Input parameters:

- `user_id` (string, required): Your own id for the user.

### `get_authenticator` (~55 tokens)

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.

Input parameters:

- `user_id` (string, required): Your own id for the user.

### `remove_authenticator` (~43 tokens)

Remove a user's authenticator

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

Input parameters:

- `user_id` (string, required): Your own id for the user.

### `unlock_user` (~45 tokens)

Unlock a user

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

Input parameters:

- `user_id` (string, required): Your own id for the user.

### `export_user` (~63 tokens)

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.

Input parameters:

- `user_id` (string, required): Your own id for the user.

### `get_consent` (~41 tokens)

Get a user's consent

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

Input parameters:

- `user_id` (string, required): Your own id for the user.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-signops-signops/api#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 28

## Common questions

### What is the SignOps MCP server?

SignOps is an MCP server listed in the public MCP registry as dev.signops/signops. Send push to Android, iOS and the web, and ask a trusted phone to approve a login, from your agent. This page covers its hosted endpoint (https://api.signops.dev/mcp).

### Is the SignOps MCP server safe to use?

SignOps scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SignOps MCP server expose?

SignOps exposes 23 tools: send_push, get_push, list_pushes, cancel_push, register_device, and 18 more. Their descriptions and schemas cost roughly 1,369 tokens of context every time the server is loaded.

### Does the SignOps MCP server require authentication?

Yes. SignOps asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the SignOps MCP server still maintained?

SignOps is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SignOps MCP server?

VerifyMCP ran 12 checks on SignOps, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SignOps: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.signops.dev/mcp
- Authorisation metadata: https://api.signops.dev/.well-known/oauth-protected-resource/mcp
- Website: https://signops.dev/docs/#mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-signops-signops/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-signops-signops/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-signops-signops/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-signops-signops/api