SignOps

Name: SignOps
Author: dev.signops

MCP serverMCP

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

by dev.signopshomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"signops","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability13/13 checks ok

30 days ago

when	check	result	http	latency	detail
34 min ago	mcp initialize	ok	200	35 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
9 h ago	mcp initialize	ok	200	45 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
17 h ago	mcp initialize	ok	200	30 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
25 h ago	mcp initialize	ok	200	73 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
33 h ago	mcp initialize	ok	200	13 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
2 d ago	mcp initialize	ok	200	38 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
2 d ago	mcp initialize	ok	200	42 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
2 d ago	mcp initialize	ok	200	54 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
3 d ago	mcp initialize	ok	200	42 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools
3 d ago	mcp initialize	ok	200	41 ms	server signops 1.0.0 · protocol 2025-06-18 · 23 tools

Tools observed via MCP handshake

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, s
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 hist
get_consent — The latest consent answer per purpose for one user, like marketing_push, and the history.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrydev.signops/signops

first seen 4 d ago · fetched 7 h agoopen ↗

Field history (6 recent events)

4 d ago · declared · summary → "Send push to Android, iOS and the web, and ask a trusted phone to approve a login, from your agent."
4 d ago · declared · description → "Send push to Android, iOS and the web, and ask a trusted phone to approve a login, from your agent."
4 d ago · declared · publisherName → "dev.signops"
4 d ago · declared · homepageUrl → "https://signops.dev/docs/#mcp"
4 d ago · declared · version → "1.0.0"
4 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from