Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Notifyre MCP by usefulapi

REMOTE · NOTIFYRE.USEFULAPI.IO

Read Notifyre SMS, replies, faxes, numbers, prices and contacts; send SMS to up to 10 numbers.

65 Trust /100

Last scanned (8 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Communication

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security78
Transport & Reachability0
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2756 tokens (~131/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 14 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • The server now declares the “prompts” capability functional
    • First check of Schema quality: 100 functional
    • New prompt “getting_started” functional
    • Server version: 1.0.0 → 1.1.0 functional
  • 13 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Probed https://notifyre.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of notifyre.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 302

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://notifyre.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://notifyre.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://notifyre.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://notifyre.usefulapi.io/mcp
Authorisation server https://notifyre.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://notifyre.usefulapi.io/mcp Redirected 302 https://usefulapi.io/notifyre/
http (plaintext) http://notifyre.usefulapi.io/mcp Inconclusive 302 http://notifyre.usefulapi.io/mcp
MCP tools · 21 exposed · ~2,547 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
notifyre_add_contacts_to_groups ~90

WRITE: adds existing contacts to existing groups (up to 100 contacts and 20 groups). Contacts keep their other groups. Adding a contact to a group does not send anything, but a later send to that group reaches it. Notifyre API: POST /addressbook/groups/contacts.

NameTypeReqDescription
contact_idsarrayyesContact ids.
group_idsarrayyesGroup ids.

No output schema declared.

No examples provided.

notifyre_create_contact ~191

WRITE: adds one contact to the Notifyre address book. Give at least a name or a number. Numbers in international format (e.g. +61412345678). groups takes existing group ids; group_name puts the contact in that group and CREATES the group if it does not exist. Creating the same contact twice may make a duplicate. Notifyre API: POST /addressbook/contacts.

NameTypeReqDescription
emailstring–Email address.
fax_numberstring–Fax number, international format.
first_namestring–Given name.
group_idsarray–Existing group ids to add the contact to.
group_namestring–Group name to add the contact to (created if missing).
last_namestring–Family name.
mobile_numberstring–Mobile number, international format.
organizationstring–Organization or company.

No output schema declared.

No examples provided.

notifyre_create_group ~42

WRITE: creates one address book group with the given name. Notifyre API: POST /addressbook/groups.

NameTypeReqDescription
namestringyesThe group name.

No output schema declared.

No examples provided.

notifyre_get_contact ~58

Get one contact: names, organization, email, fax and mobile number, groups, custom fields, unsubscribed flag. Notifyre API: GET /addressbook/contacts/{id}.

NameTypeReqDescription
contact_idstringyesThe contact id.

No output schema declared.

No examples provided.

notifyre_get_sent_sms ~73

Get one sent SMS message with every recipient: status, delivery status, message parts, cost. Use the id from notifyre_list_sent_sms or notifyre_send_sms. Notifyre API: GET /sms/send/{id}.

NameTypeReqDescription
message_idstringyesThe SMS message id (not the friendly id).

No output schema declared.

No examples provided.

notifyre_get_sms_recipient ~77

Get the text and delivery details of one recipient of a sent SMS (status, parts, cost). Notifyre API: GET /sms/send/{messageId}/recipients/{recipientId}.

NameTypeReqDescription
message_idstringyesThe SMS message id.
recipient_idstringyesThe recipient id from get_sent_sms.

No output schema declared.

No examples provided.

notifyre_get_sms_reply ~60

Get one received SMS reply with its text, sender and receiving number. Use the replyID from notifyre_list_sms_replies. Notifyre API: GET /sms/received/{id}.

NameTypeReqDescription
reply_idstringyesThe reply id.

No output schema declared.

No examples provided.

notifyre_list_brands ~37

List the account's registered 10DLC brands (US SMS sender registration). Notifyre API: GET /numbers/brands.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

notifyre_list_campaigns ~42

List the account's 10DLC campaigns (US SMS use-case registrations) and their status. Notifyre API: GET /numbers/campaigns.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

notifyre_list_contacts ~212

Search the address book. search_query matches the name; type FaxNumber or MobileNumber keeps contacts that have that number; group_ids limits to groups. Page numbers start at 0. Contacts that unsubscribed are left out unless include_unsubscribed is true. The unsubscribe key of a contact is never shown. Notifyre API: POST /addressbook/contacts/search (a read).

NameTypeReqDescription
group_idsarray–Only contacts in these group ids.
include_unsubscribedboolean–Also return contacts that unsubscribed (default false).
limitinteger–Page size, 1 to 100 (default 20).
pageinteger–Page number, from 0 (default 0).
search_querystring–Text in the contact's name.
sort_bystring–Sort field (default name).
sort_dirstring–asc or desc (default asc).
typestring–Only contacts that have this kind of number.

No output schema declared.

No examples provided.

notifyre_list_fax_cover_pages ~51

List the fax cover page templates of the account (name and whether it is the default). The HTML of each template is left out. Notifyre API: GET /fax/coverpages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

notifyre_list_fax_numbers ~37

List the account's fax numbers (E.164, region, status). Notifyre API: GET /fax/numbers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

notifyre_list_fax_prices ~44

List the price of sending a fax per destination country (country code, calling prefix, price, currency). Notifyre API: GET /fax/send/prices.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

notifyre_list_groups ~70

List the address book groups with their contact counts. Notifyre API: GET /addressbook/groups.

NameTypeReqDescription
search_querystring–Text in the group name.
sort_bystring–Sort field (default name).
sort_dirstring–asc or desc (default asc).

No output schema declared.

No examples provided.

notifyre_list_received_faxes ~188

List faxes received on the account's fax numbers (sender, number, time, pages, duration, read flag). The fax documents are not downloaded. Without from_date the window is the last 30 days. Page with skip = next_skip. Notifyre API: GET /fax/received.

NameTypeReqDescription
from_datestring–Start, ISO 8601 date or date-time with timezone. Default: 30 days before to_date.
limitinteger–Page size, 1 to 100 (default 20).
skipinteger–Records to skip (default 0).
sortstring–asc or desc by date (default desc).
to_datestring–End, ISO 8601 date or date-time. Default: now.
to_numberstring–Only faxes received on this account fax number.

No output schema declared.

No examples provided.

notifyre_list_sent_faxes ~199

List faxes sent from the account (recipient, pages, quality, status, failure reason). Without from_date the window is the last 30 days. Filter by status (accepted, successful, in_progress, failed, queued). Page with skip = next_skip. Notifyre API: GET /fax/send.

NameTypeReqDescription
from_datestring–Start, ISO 8601 date or date-time with timezone. Default: 30 days before to_date.
limitinteger–Page size, 1 to 100 (default 20).
searchstring–Filter by fax id or reference.
skipinteger–Records to skip (default 0).
sortstring–asc or desc by date (default desc).
statusstring–Only faxes with this status.
to_datestring–End, ISO 8601 date or date-time. Default: now.

No output schema declared.

No examples provided.

notifyre_list_sent_sms ~259

List SMS messages sent from the account, newest first by default, with recipient, status and cost. Without from_date the window is the last 30 days. Filter by status (processing, submitted, sent, failed), numbers, or a message id in search. Page with skip = next_skip. Notifyre API: GET /sms/send.

NameTypeReqDescription
from_datestring–Start, ISO 8601 date (2026-10-01) or date-time with timezone. Default: 30 days before to_date.
from_numberstring–Number the SMS was sent from.
limitinteger–Page size, 1 to 100 (default 20).
searchstring–Filter by message id or scheduled job id.
skipinteger–Records to skip (default 0).
sortstring–asc or desc by date (default desc).
statusstring–Only messages with this status.
to_datestring–End, ISO 8601 date (2026-10-31, to the end of that UTC day) or date-time. Default: now.
to_numberstring–Destination number the SMS was sent to.

No output schema declared.

No examples provided.

notifyre_list_sms_numbers ~58

List the account's SMS numbers (E.164, status, 10DLC campaign) and approved alphanumeric sender IDs. Use one of them as `from` when sending. Notifyre API: GET /sms/numbers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

notifyre_list_sms_prices ~60

List the price of one SMS per destination country (country code, calling prefix, price, currency). Check it before sending: the cost of a send is price x message parts x recipients. Notifyre API: GET /sms/send/prices.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

notifyre_list_sms_replies ~254

List SMS replies received on the account's numbers. Without from_date the window is the last 30 days. from_number and to_number must be given together. include_reply_content adds the reply texts (then at most 20 per page). Page with skip = next_skip. Notifyre API: GET /sms/received.

NameTypeReqDescription
from_datestring–Start, ISO 8601 date or date-time with timezone. Default: 30 days before to_date.
from_numberstring–Number the reply came from. Needs to_number as well.
include_reply_contentboolean–Include the reply texts (default false; limit is then capped at 20).
limitinteger–Page size, 1 to 100 (default 20).
recipient_idstring–Only replies to this SMS recipient id.
skipinteger–Records to skip (default 0).
sortstring–asc or desc by date (default desc).
to_datestring–End, ISO 8601 date or date-time. Default: now.
to_numberstring–Account number that received the reply. Needs from_number as well.

No output schema declared.

No examples provided.

notifyre_send_sms ~445

WRITE: SENDS REAL SMS to real people and SPENDS the prepaid balance of the user's Notifyre account; it cannot be undone or recalled and is never retried. One text to 1 to 10 mobile numbers in international format with "+" (e.g. +61412345678); no contacts, no groups, no scheduling. Cost = price per message part (see notifyre_list_sms_prices; it depends on the destination country) x number of parts x number of recipients; the text may be up to 640 characters (160 per part, 70 with emoji or non-GSM characters, a little less per part when it is longer). Only send what the user explicitly asked for: confirm the exact text, the recipients and the sender first. Recipients must have agreed to receive messages. A commercial SMS needs an opt-out (Australia: Spam Act 2003; Notifyre Terms and Conditions 13.5): set add_unsubscribe_link true to append Notifyre's opt-out link, or put your own opt-out instruction in the text. The default is false, so the requirement is yours to meet. US numbers need a registered 10DLC campaign. Omit `from` to send from a Notifyre shared number. An unclear result (timeout, HTTP 5xx) means the message may still have been sent: check notifyre_list_sent_sms before trying again. Notifyre API: POST /sms/send.

NameTypeReqDescription
add_unsubscribe_linkboolean–Append Notifyre's opt-out link to the text (default false). A commercial SMS needs an opt-out: set true, or write your own opt-out line. Adds characters, so it can add a part.
bodystringyesThe message text.
campaign_namestring–Optional reference name for this send.
fromstring–Optional sender: one of the account's SMS numbers or sender IDs (see notifyre_list_sms_numbers). Omit to use a Notifyre shared number.
toarrayyes1 to 10 mobile numbers in international format with country code and "+", e.g. +61412345678.

No output schema declared.

No examples provided.

Install

How do I install the Notifyre MCP by usefulapi server?

Notifyre MCP by usefulapi is a hosted endpoint at https://notifyre.usefulapi.io/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.

remote · notifyre.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-notifyre 'https://notifyre.usefulapi.io/mcp'
Common questions

What is the Notifyre MCP by usefulapi server?

Notifyre MCP by usefulapi is listed in the public MCP registry as io.usefulapi/notifyre. Read Notifyre SMS, replies, faxes, numbers, prices and contacts; send SMS to up to 10 numbers. This page covers its hosted endpoint (https://notifyre.usefulapi.io/mcp).

Is the Notifyre MCP by usefulapi server safe to use?

Notifyre MCP by usefulapi scores 65 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 Notifyre MCP by usefulapi server expose?

Notifyre MCP by usefulapi exposes 21 tools: notifyre_list_sent_sms, notifyre_get_sent_sms, notifyre_get_sms_recipient, notifyre_list_sms_replies, notifyre_get_sms_reply, and 16 more. Their descriptions and schemas cost roughly 2,547 tokens of context every time the server is loaded.

Does the Notifyre MCP by usefulapi server require authentication?

Yes. Notifyre MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Notifyre MCP by usefulapi server still maintained?

Notifyre MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.