All servers · Email & messaging
NOTIFY
io.github.n0t1fy/notify-sms-georgia · v0.2.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | tools |
| Tool definitions | 5 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
SMS verification codes for Georgia (+995), sent and checked. Try test codes with a free test key.
Connect
streamable-http · https://api.n0t1fy.dev/mcp
claude mcp add --transport http notify-sms-georgia https://api.n0t1fy.dev/mcp{
"mcpServers": {
"notify-sms-georgia": {
"url": "https://api.n0t1fy.dev/mcp"
}
}
}Tools as reported by the server
create_test_keyGet 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 NOTsend_messageSend one transactional SMS to a Georgian mobile number. The text comes from a built-in template; there is no free text. With a test key (sk_test_) nothing is really sent: a simulator answers. These recipients simulate outcomes: +995512345671 rejected (status `failed`); +995512345672 provider unreachstart_verificationVerify 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 numbercheck_verificationCheck 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 neget_messageRead 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.
Tool changes
- 2026-10-16: create_test_key, send_message, start_verification, check_verification, get_message
- 2026-10-15: create_test_key, send_message, get_message
Website · JSON · Text for agents · Registry updated 2026-10-15