# NOTIFY (remote · api.n0t1fy.dev)

SMS verification codes for Georgia (+995), sent and checked. Try test codes with a free test key.

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

## Components

- remote · `api.n0t1fy.dev`: 78/100 (this document), [markdown](https://verifymcp.io/servers/n0t1fy-notify-sms-georgia/api.md), [page](https://verifymcp.io/servers/n0t1fy-notify-sms-georgia/api)

## Channel facts

- Endpoint: `https://api.n0t1fy.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**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

NOTIFY is a hosted endpoint at https://api.n0t1fy.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 n0t1fy-notify-sms-georgia 'https://api.n0t1fy.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "n0t1fy-notify-sms-georgia": {
      "url": "https://api.n0t1fy.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "n0t1fy-notify-sms-georgia": {
      "type": "http",
      "url": "https://api.n0t1fy.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.n0t1fy-notify-sms-georgia]
url = "https://api.n0t1fy.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add n0t1fy-notify-sms-georgia --url 'https://api.n0t1fy.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  n0t1fy-notify-sms-georgia:
    url: "https://api.n0t1fy.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "n0t1fy-notify-sms-georgia": {
      "Transport": "http",
      "Url": "https://api.n0t1fy.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add n0t1fy-notify-sms-georgia -t streamable-http -u 'https://api.n0t1fy.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "n0t1fy-notify-sms-georgia": {
      "type": "http",
      "url": "https://api.n0t1fy.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-05 (score 78, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Stability: 0.70 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-03 (score 78, +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-31 (score 77, +1)

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

### 2026-10-30 (score 76, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “send_message” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 409 → 494
- [cosmetic] “send_message” reworded the description of “template”
- [cosmetic] “send_message” reworded the description of “variables”

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

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

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

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

### 2026-10-24 (score 74, 0)

- [security regression] DNSSEC: pass → fail

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

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

## MCP tools (5)

### `create_test_key` (~192 tokens)

Get a NOTIFY test key

Get an sk_test_ API key instantly, with no account and no human. A test key never sends a real SMS and never spends credits, so a whole integration can be built and verified with it. Pass it as `api_key` to send_message and get_message, and keep it in the application's configuration (for example NOTIFY_API_KEY), never in source code. The result also has a `claim_url` for a human: opening it lets them sign in and take over the project. Anyone who opens it, signs in and confirms becomes the owner: give it only to the person who will own the project, and do not paste it into shared logs or tickets. Real SMS need an sk_live_ key that the human creates on the dashboard (https://n0t1fy.dev/dashboard). Limited to a few keys per minute and per day for each address: reuse a key you already have.

### `send_message` (~974 tokens)

Send a code by SMS

Send one transactional SMS to a Georgian mobile number. The text comes from a built-in template; there is no free text (every template: https://n0t1fy.dev/templates).

Team templates (`service_down`, `service_up`, `incident_opened`, `support_ticket_urgent`, `job_failed`, `agent_alert`) go only to numbers the project's owner confirmed on the dashboard's team page; with a test key, use the test numbers +995512345670 to +995512345679. A `recipient_not_on_team` error means the number is not confirmed on the team: ask the human to add it on the dashboard, and never retry by yourself. With a live key, a `service` or `job` must be a name on the owner's list there.

With a test key (sk_test_) nothing is really sent: a simulator answers. These recipients simulate outcomes: +995512345671 rejected (status `failed`); +995512345672 provider unreachable (error `provider_unavailable`: nothing was sent, retry with the same idempotency_key); +995512345673 ambiguous (status `unknown`); +995512345674 accepted, then `undeliverable`. Any other valid number is accepted, then `delivered`, within about 30 seconds. With a live key it sends a real SMS and spends one credit per segment.

Read `message.status` in the result. `submitted`: the provider accepted it, which is not yet delivery to the phone. `failed`: refused; `message.error` says why. `unknown`: it may or may not have been sent, so do not send it again automatically. `replayed: true`: this idempotency_key and request were already processed, and no second SMS was sent. Call get_message to learn the final outcome.

Input parameters:

- `api_key` (string): An sk_test_ key, for example from create_test_key. Leave it out to use the key in this MCP server's Authorization header. A live key (sk_live_) is refused here: tool arguments are kept in the convers…
- `idempotency_key` (string, required): A new unique value (a UUID) for each logical message. Reuse it only to retry the identical request: the retry then returns the original message instead of sending a second SMS.
- `locale` (string): Language of the message: `ka` (Georgian, the default) or `en`.
- `template` (string, required): Which message to send. Message text is never free-form: every message is rendered from one of these templates. - `verification_code` (`code`): Your verification code is {code}. Do not share it with…
- `to` (string, required): Recipient in E.164 format: `+9955` followed by eight digits. No other country or format is accepted, and numbers are never normalized on your behalf.
- `variables` (object, required): Values for the template's placeholders, all as JSON strings. A `code` is 4 to 8 digits; `minutes` is 1 to 999; an `incident` or `ticket` 1 to 8 digits; a `count` 1 to 99; an `agent` `your_agent` or `…

### `start_verification` (~536 tokens)

Send a verification code that NOTIFY makes

Verify a Georgian mobile number: NOTIFY makes a random six-digit code and sends it by SMS with a built-in template. The code is never shown to you: ask the human for the code they received, then call check_verification. A code works for 10 minutes and 5 checks, once; a new start for the same number replaces it.

With a test key (sk_test_), only the test numbers +995512345670 to +995512345679 are accepted and their code is always 000000; nothing is sent. At most 5 starts a minute go to one number, so spread test starts over the ten test numbers. +995512345671 simulates a refused SMS (status `failed`), +995512345672 an unreachable provider (error `provider_unavailable`: nothing was sent, retry with the same idempotency_key), +995512345673 an SMS that may or may not have arrived (still `pending`). With a live key it sends a real SMS and spends one credit.

\`replayed: true` means this idempotency_key and request were already processed and no second SMS was sent; the verification it shows may say `approved` by then, which is not a check result. On `too_many_verifications` (5 an hour or 10 in a rolling 24 hours to one number), tell the human when they can try again (`retry_at`), and never retry by yourself.

Input parameters:

- `api_key` (string): An sk_test_ key, for example from create_test_key. Leave it out to use the key in this MCP server's Authorization header. A live key (sk_live_) is refused here: tool arguments are kept in the convers…
- `idempotency_key` (string, required): A new unique value (a UUID) for each code you want sent. Reuse it only to retry the identical request: the retry then returns the original verification instead of sending a second SMS.
- `locale` (string): Language of the message: `ka` (Georgian, the default) or `en`.
- `template` (string): Which message carries the code. NOTIFY fills in the code, and the minutes where the template names them (10).
- `to` (string, required): The phone number to verify, in E.164 format: `+9955` followed by eight digits. With a test key (`sk_test_`), only the test numbers +995512345670 to +995512345679 are accepted, and their code is alway…

### `check_verification` (~296 tokens)

Check a verification code

Check the code the human typed, for the number the code was sent to. The result is the verification only when it is approved; every other outcome is a tool error with an `error.code`. Let the user in only when a check answers `200` with status `approved`; treat every other answer, a timeout and a network error as not approved.

Errors: `incorrect_code` (attempts remain), `too_many_attempts` (start a new verification), `recipient_mismatch` (`to` is not the number the code was sent to), `verification_expired`, `verification_closed` (already approved or replaced), `verification_not_found`. A wrong code costs an attempt, and five close the verification: do not retry a check by yourself; ask the human for the code again.

Input parameters:

- `api_key` (string): An sk_test_ key, for example from create_test_key. Leave it out to use the key in this MCP server's Authorization header. A live key (sk_live_) is refused here: tool arguments are kept in the convers…
- `code` (string, required): The six digits the human typed, as a string.
- `to` (string, required): The number the code was sent to, which your application is about to mark as verified.
- `verification_id` (string, required): The verification `id` from start_verification (ver_…).

### `get_message` (~203 tokens)

Read a message's status

Read the current state of a message sent with a key of the same project. Poll only while `status` is `queued` or `submitted`: `delivered`, `undeliverable` and `failed` are final, and `unknown` never changes. Wait about 2 seconds before the first read and double the wait each time, up to 30 seconds. Always set a time limit (two minutes is generous for a test message); when it passes, treat the message as unconfirmed and do not send it again.

Input parameters:

- `api_key` (string): An sk_test_ key, for example from create_test_key. Leave it out to use the key in this MCP server's Authorization header. A live key (sk_live_) is refused here: tool arguments are kept in the convers…
- `message_id` (string, required): The message `id` from send_message, such as msg_01J8….

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 71
- 2026-10-15: 71
- 2026-10-14: 70

## Common questions

### What is the NOTIFY MCP server?

NOTIFY is an MCP server listed in the public MCP registry as io.github.n0t1fy/notify-sms-georgia. SMS verification codes for Georgia (+995), sent and checked. Try test codes with a free test key. This page covers its hosted endpoint (https://api.n0t1fy.dev/mcp).

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

NOTIFY 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 NOTIFY MCP server expose?

NOTIFY exposes 5 tools: create_test_key, send_message, start_verification, check_verification, get_message. Their descriptions and schemas cost roughly 2,201 tokens of context every time the server is loaded.

### Does the NOTIFY MCP server require authentication?

Its publisher declares no required credentials for NOTIFY. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the NOTIFY MCP server still maintained?

NOTIFY is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 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://api.n0t1fy.dev/mcp
- Website: https://n0t1fy.dev/api#mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/n0t1fy-notify-sms-georgia/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/n0t1fy-notify-sms-georgia/api.json
- HTML version of this page: https://verifymcp.io/servers/n0t1fy-notify-sms-georgia/api