NOTIFY
SMS verification codes for Georgia (+995), sent and checked. Try test codes with a free test key.
| Endpoint | https://api.n0t1fy.dev/mcp (streamable-http) |
|---|---|
| Registry version | 0.2.0 |
| Now | 5 tools · grade C (69) · pin ts_94b3b1480b0843dd7b176a8658b3517c · protocol 2025-06-18 |
| First / last listed | 2026-11-08 03:45 UTC / 2026-11-08 03:45 UTC |
| Grade over time | 2026-11-08: C (69), 5 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: create_test_key send_message start_verification check_verification get_message
create_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 t params: none |
send_message | 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 numb params: to*, template*, variables*, locale, idempotency_key*, api_key |
start_verification | 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 a params: to*, template, locale, idempotency_key*, api_key |
check_verification | 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 params: verification_id*, to*, code*, api_key |
get_message | 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 mess params: message_id*, api_key |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.