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.
Available components
Last scanned (9 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1467 tokens (~63/item across 23 items; 23 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 28 Oct 26 +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.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 +41
- Transport: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 25 Oct 26 28
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.signops.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=signops.dev | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6011be416f13a249131d04f0a66ad6b2 |
| SANs: signops.dev, api.signops.dev, *.api.signops.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.signops.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| signops.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.signops.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.signops.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_approval Cancel an approval ~28
Cancel a pending approval request.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The approval id, apr_... |
No output schema declared.
No examples provided.
cancel_push Cancel a scheduled push ~33
Cancel a push that is scheduled and has not started sending.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The push id, msg_... |
No output schema declared.
No examples provided.
create_approval Ask a user to approve ~75
Send an approval request to the user's trusted phone, with number matching. The user must have a phone enrolled through the SignOps SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | What they are approving, up to 120 characters, like Sign in from Chrome on Windows. |
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
delete_template Delete a template ~34
Delete a template by name. Pushes already made from it are not changed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The template name. |
No output schema declared.
No examples provided.
export_user Export a user's data ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
get_approval Get an approval ~38
An approval request's status: pending, approved, denied, expired or cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The approval id, apr_... |
No output schema declared.
No examples provided.
get_authenticator Get a user's authenticator ~55
Whether a user has an authenticator app (TOTP) confirmed, when it was last used, backup codes left, and whether wrong codes have locked them.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
get_consent Get a user's consent ~41
The latest consent answer per purpose for one user, like marketing_push, and the history.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
get_push Get a push ~37
One push by id: status, devices, sent and failed, per platform.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The push id, msg_... |
No output schema declared.
No examples provided.
get_template Get a template ~27
One template by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The template name, like payment_received. |
No output schema declared.
No examples provided.
list_devices List a user's devices ~43
The devices registered for one user id, newest first, with platform and whether each is trusted for approvals.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
list_passkeys List a user's passkeys ~32
The passkeys registered for one user id.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
list_pushes List pushes ~52
Pushes, newest first. On the Free plan only pushes still to go are listed (no delivery logs).
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | The next value from the previous page. |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_templates List templates ~15
Saved push templates with their fields.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_topics List topics ~16
Topics with how many users each has.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_device Register a device ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional label, like Rushi's iPhone. |
| platform | string | yes | – |
| token | string | yes | The push token. |
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
remove_authenticator Remove a user's authenticator ~43
Remove a user's authenticator app and backup codes, for a lost phone. They can enrol again.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
remove_device Remove a device ~33
Remove one device by id; it gets no more pushes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The device id, dev_... |
No output schema declared.
No examples provided.
save_template Save a template ~111
Create or replace a template. Put {{field}} where a value goes, or {{field|default}} for one with a fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Lowercase letters, digits and underscores. |
| title | string | – | Title, with {{fields}}. |
No output schema declared.
No examples provided.
send_push Send a push ~360
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
subscribe_topic Subscribe a user to a topic ~59
Add a user to a topic. The topic exists once it has a user.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Up to 64 letters, digits, dashes, dots or underscores. |
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
unlock_user Unlock a user ~45
Clear the lock that five wrong codes in 15 minutes put on a user, and their count of wrong codes.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
unsubscribe_topic Unsubscribe a user from a topic ~39
Take a user off a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | The topic name. |
| user_id | string | yes | Your own id for the user. |
No output schema declared.
No examples provided.
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.
remote · api.signops.dev
claude mcp add --transport http dev-signops-signops 'https://api.signops.dev/mcp'
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.