# useSignal (remote · www.usesignal.dev)

QR codes, JSON diff/format, hashes, JWT, cron, timestamps, placeholders, flowcharts, forms, regex.

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

## Components

- remote · `www.usesignal.dev`: 78/100 (this document), [markdown](https://verifymcp.io/servers/sanket-naik-usesignal/www.md), [page](https://verifymcp.io/servers/sanket-naik-usesignal/www)

## Channel facts

- Endpoint: `https://www.usesignal.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 47/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1150 tokens (~88/item across 13 items; 12 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 68/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 5% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "usesignal_test_regex" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 13 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.
  - Supports UI / widget rendering.

## Install

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

useSignal is a hosted endpoint at https://www.usesignal.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 sanket-naik-usesignal 'https://www.usesignal.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sanket-naik-usesignal": {
      "url": "https://www.usesignal.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sanket-naik-usesignal": {
      "type": "http",
      "url": "https://www.usesignal.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sanket-naik-usesignal]
url = "https://www.usesignal.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sanket-naik-usesignal": {
      "type": "remote",
      "url": "https://www.usesignal.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sanket-naik-usesignal --url 'https://www.usesignal.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sanket-naik-usesignal:
    url: "https://www.usesignal.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sanket-naik-usesignal": {
      "Transport": "http",
      "Url": "https://www.usesignal.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sanket-naik-usesignal -t streamable-http -u 'https://www.usesignal.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sanket-naik-usesignal": {
      "type": "http",
      "url": "https://www.usesignal.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-02 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 78, +1)

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

### 2026-10-29 (score 77, +1)

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

### 2026-10-27 (score 76, +1)

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

### 2026-10-25 (score 75, +1)

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

### 2026-10-23 (score 74, +1)

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

### 2026-10-21 (score 73, +1)

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

### 2026-10-19 (score 72, +1)

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

## MCP tools (12)

### `usesignal_generate_form` (~91 tokens)

Generate an editable form from a JSON object. Returns nested field paths, JSON Schema, HTML, React JSX and config exports. Arrays and nulls use JSON textareas. Values are processed in memory; avoid secrets. To show an interactive preview, call usesignal_open_workbench with this result input.

Input parameters:

- `json` (string, required)
- `overrides` (array)
- `title` (string)

### `usesignal_generate_colors` (~76 tokens)

Generate light and dark semantic color tokens from a six-digit hex brand color. Returns a shade scale, measured text contrast checks and CSS, JSON and Tailwind exports. This measures listed color pairs only, not whole-page accessibility. Call usesignal_open_workbench with the result input to preview.

Input parameters:

- `baseColor` (string, required)

### `usesignal_test_regex` (~88 tokens)

Execute a JavaScript regular expression against text and expected match/non-match test cases. Returns indexed matches and capture groups. Flags use JavaScript semantics. Execution times out after 500ms. Call usesignal_open_workbench with result input to highlight matches.

Input parameters:

- `flags` (string)
- `pattern` (string, required)
- `tests` (array)
- `text` (string, required)

### `usesignal_generate_qr` (~191 tokens)

Generate a scannable QR code for a link, text, Wi-Fi network, contact card (vCard), email, SMS, phone number, WhatsApp chat or UPI payment. Returns the encoded payload, an SVG file and a PNG preview image. values by type: url{url}; text{text}; wifi{ssid,password,security:WPA|WEP|nopass,hidden}; vcard{firstName,lastName,phone,email,org,title,website,address}; email{to,subject,body}; sms{phone,message}; phone{phone}; whatsapp{phone,message}; upi{vpa,name,amount,note}.

Input parameters:

- `dark` (string)
- `errorCorrection` (string)
- `light`
- `margin` (integer)
- `moduleStyle` (string)
- `type` (string, required)
- `values` (object, required)

### `usesignal_encode_decode` (~96 tokens)

Exact text transforms: Base64 encode/decode (UTF-8), URL encode/decode, decode a JWT header and payload with readable exp/iat/nbf dates (the signature is not verified), or hash text with MD5, SHA-1, SHA-256 and SHA-512. Use this instead of computing hashes or Base64 by hand.

Input parameters:

- `operation` (string, required)
- `text` (string, required)

### `usesignal_explain_cron` (~90 tokens)

Explain a standard 5-field cron expression (minute hour day-of-month month day-of-week) in plain English and list its next run times in a given time zone, handling daylight saving time.

Input parameters:

- `count` (integer)
- `expression` (string, required)
- `timeZone` (string): IANA time zone, e.g. Asia/Kolkata or America/New_York

### `usesignal_convert_timestamp` (~81 tokens)

Convert a Unix timestamp (seconds or milliseconds) or an ISO 8601 date into ISO, UTC, epoch seconds/milliseconds, a relative time and the local time in a given time zone.

Input parameters:

- `timeZone` (string): IANA time zone, e.g. Asia/Kolkata or America/New_York
- `value` (string, required)

### `usesignal_diff_json` (~82 tokens)

Compare two JSON documents structurally and list every added, removed and changed value with its JSONPath. Numbers compare exactly. Arrays match by content by default, so an inserted item shows as one addition; use arrays:"position" to compare index by index.

Input parameters:

- `arrays` (string)
- `left` (string, required)
- `right` (string, required)

### `usesignal_format_json` (~97 tokens)

Validate, pretty-print or minify JSON, optionally sorting keys. Invalid JSON reports the exact line and column; with repair (default on) it fixes common problems such as trailing commas, single quotes, comments and unquoted keys, and lists each fix.

Input parameters:

- `indent` (string)
- `json` (string, required)
- `mode` (string)
- `repair` (boolean)
- `sortKeys` (boolean)

### `usesignal_placeholder_image` (~105 tokens)

Create a placeholder image URL (served by usesignal.dev) plus HTML, Markdown and CSS snippets, for mockups, prototypes, seed data and layouts. Width and height up to 4000 px.

Input parameters:

- `background` (string)
- `color`
- `height` (integer, required)
- `pattern` (string)
- `radius` (integer)
- `style` (string)
- `text` (string)
- `width` (integer, required)

### `usesignal_flowchart` (~85 tokens)

Turn JavaScript/TypeScript code, arrow steps or Mermaid-style arrows into a flowchart, returned as Mermaid source and an SVG diagram. Steps mode uses one flow per line: "Start -> Validate -> Save" and branches like "Validate -- No --> Show error".

Input parameters:

- `direction` (string)
- `input` (string, required)
- `mode` (string, required)

### `usesignal_open_workbench` (~61 tokens)

Open useSignal workbench

Show the editable useSignal UI. First call a useSignal data tool, then pass its returned input and matching tool name. Recomputes from validated inputs; no shared state.

Input parameters:

- `input` (object, required)
- `tool` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sanket-naik-usesignal/www#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 69
- 2026-10-12: 69
- 2026-10-10: 68
- 2026-10-09: 67
- 2026-10-07: 66
- 2026-10-06: 66
- 2026-10-04: 65

## Common questions

### What is the useSignal MCP server?

useSignal is an MCP server listed in the public MCP registry as io.github.sanket-naik/usesignal. QR codes, JSON diff/format, hashes, JWT, cron, timestamps, placeholders, flowcharts, forms, regex. This page covers its hosted endpoint (https://www.usesignal.dev/mcp).

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

useSignal scores 78 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 useSignal MCP server expose?

useSignal exposes 12 tools: usesignal_generate_form, usesignal_generate_colors, usesignal_test_regex, usesignal_generate_qr, usesignal_encode_decode, and 7 more. Their descriptions and schemas cost roughly 1,143 tokens of context every time the server is loaded.

### Does the useSignal MCP server require authentication?

No. We connected to useSignal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the useSignal MCP server still maintained?

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

## Links

- Remote endpoint: https://www.usesignal.dev/mcp
- Repository: https://github.com/sanket-naik/usesignal-claude-plugin
- Website: https://www.usesignal.dev/
- Changelog RSS feed: https://verifymcp.io/servers/sanket-naik-usesignal/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/sanket-naik-usesignal/www.json
- HTML version of this page: https://verifymcp.io/servers/sanket-naik-usesignal/www