# io.usefulapi/smile-io (remote · smile-io.usefulapi.io)

Look up loyalty customers, points history, rewards and VIP tiers, and add points or activities.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `smile-io.usefulapi.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-smile-io/smile-io.md), [page](https://verifymcp.io/servers/io-usefulapi-smile-io/smile-io)

## Channel facts

- Endpoint: `https://smile-io.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1731 tokens (~123/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/smile-io MCP server?

io.usefulapi/smile-io is a hosted endpoint at https://smile-io.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-smile-io 'https://smile-io.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-smile-io": {
      "url": "https://smile-io.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-smile-io": {
      "type": "http",
      "url": "https://smile-io.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-smile-io]
url = "https://smile-io.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-smile-io": {
      "type": "remote",
      "url": "https://smile-io.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-smile-io --url 'https://smile-io.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-smile-io:
    url: "https://smile-io.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-smile-io": {
      "Transport": "http",
      "Url": "https://smile-io.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-smile-io -t streamable-http -u 'https://smile-io.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-smile-io": {
      "type": "http",
      "url": "https://smile-io.usefulapi.io/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-10-03 (score 78, +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.

### 2026-10-02 (score 77, 0)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 77, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 72, +54)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 95

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (14)

### `smile_list_customers` (~206 tokens)

List customers

List loyalty-program customers, newest first, with their points balance, state and VIP tier id. Look a customer up by exact email, or filter by state or last-updated time. Cursor-paginated (metadata.next_cursor). Smile: GET /customers.

Input parameters:

- `cursor` (string): Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page.
- `email` (string): Exact email address to look up.
- `include_vip_status` (boolean): Include each customer's vip_status object (include=vip_status).
- `limit` (integer): Maximum number of results, 1-250 (Smile default 50).
- `state` (string): candidate = not yet joined, member = in the program, disabled = excluded.
- `updated_at_min` (string): Only records updated at/after this ISO 8601 date-time, e.g. 2026-01-01T00:00:00Z.

### `smile_get_customer` (~95 tokens)

Get a customer

Fetch one customer by Smile customer ID: name, email, state, points_balance, referral_url, vip_tier_id, and optionally their VIP status with current and next tier. Smile: GET /customers/{id}.

Input parameters:

- `customer_id` (integer, required): Smile customer ID.
- `include` (array): Related objects to include, e.g. ["vip_status.vip_tier", "vip_status.next_vip_tier"].

### `smile_list_points_transactions` (~163 tokens)

List points transactions

List points transactions (every earn, spend and manual adjustment), newest first — e.g. a customer's full points history. Each has points_change (+/-), a customer-visible description and a merchant internal_note. Cursor-paginated. Smile: GET /points_transactions.

Input parameters:

- `cursor` (string): Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page.
- `customer_id` (integer): Only this customer's transactions.
- `limit` (integer): Maximum number of results, 1-250 (Smile default 50).
- `updated_at_min` (string): Only records updated at/after this ISO 8601 date-time, e.g. 2026-01-01T00:00:00Z.

### `smile_get_points_transaction` (~39 tokens)

Get a points transaction

Fetch one points transaction by ID. Smile: GET /points_transactions/{id}.

Input parameters:

- `points_transaction_id` (integer, required): Smile points transaction ID.

### `smile_list_points_products` (~135 tokens)

List points products (ways to redeem)

List points products — the rewards customers can buy with points. 'fixed' products cost points_price; 'variable' products trade variable_points_step points for variable_points_step_reward_value, between variable_points_min and variable_points_max. Each embeds its reward. Page-numbered (page, page_size); a page shorter than page_size is the last. Smile: GET /points_products.

Input parameters:

- `exchange_type` (string): Only fixed- or variable-price products.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-250 (default 50).

### `smile_get_points_product` (~50 tokens)

Get a points product

Fetch one points product (a way to redeem points) by ID, including its reward. Smile: GET /points_products/{id}.

Input parameters:

- `points_product_id` (integer, required): Smile points product ID.

### `smile_list_reward_fulfillments` (~201 tokens)

List reward fulfillments

List rewards that have been issued to customers — usually discount codes — with code, fulfillment_status (pending/issued/cancelled/failed), usage_status (used/unused/untracked), used_at and expires_at. Use customer_id to answer 'what codes does this customer have?'. Cursor-paginated. Smile: GET /reward_fulfillments.

Input parameters:

- `cursor` (string): Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page.
- `customer_id` (integer): Only this customer's rewards.
- `fulfillment_status` (string)
- `limit` (integer): Maximum number of results, 1-250 (Smile default 50).
- `updated_at_min` (string): Only records updated at/after this ISO 8601 date-time, e.g. 2026-01-01T00:00:00Z.
- `usage_status` (string)

### `smile_list_earning_rules` (~111 tokens)

List earning rules (ways to earn)

List the enabled earning rules — the ways customers earn points or rewards (placing an order, signing up, birthdays, custom activities), with reward, reward_value, earning_limit and any VIP-tier restriction. Cursor-paginated. Smile: GET /earning_rules.

Input parameters:

- `cursor` (string): Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page.
- `limit` (integer): Maximum number of results, 1-250 (Smile default 50).

### `smile_list_vip_tiers` (~71 tokens)

List VIP tiers

List the VIP program's tiers, sorted by milestone (the threshold to reach each tier), optionally with each tier's perks and entry rewards. Smile: GET /vip_tiers.

Input parameters:

- `include` (array): Nested objects to include, e.g. ["perks", "entry_rewards"].

### `smile_get_points_settings` (~37 tokens)

Get points settings

Fetch the points program's configuration, e.g. the points currency label ("Points", "Stars"). Smile: GET /points_settings.

### `smile_get_referral_settings` (~45 tokens)

Get referral settings

Fetch the referral program's configuration: whether it is active, and the sender (advocate) and receiver (friend) rewards. Smile: GET /referral_settings.

### `smile_create_points_transaction` (~175 tokens)

Adjust a customer's points balance

WRITE: add or deduct points from a customer's balance (a manual adjustment, e.g. a goodwill credit or a correction). points_change > 0 adds, < 0 deducts; Smile rejects a deduction that would make the balance negative. Undo by creating an opposite adjustment. `description` is shown to the customer; `internal_note` is merchant-only. To reward a customer for completing an action, prefer smile_create_activity. Requires the points_transaction:write scope. Smile: POST /points_transactions.

Input parameters:

- `customer_id` (integer, required): Smile customer ID.
- `description` (string): Customer-visible reason, e.g. "Points correction".
- `internal_note` (string): Merchant-only note, never shown to the customer.
- `points_change` (integer, required): Points to add (positive) or deduct (negative).

### `smile_create_activity` (~232 tokens)

Record a customer activity

WRITE: record that a customer performed an action (identified by an activity type token configured in Smile Admin, e.g. a custom 'newsletter signup' activity). Smile then asynchronously applies the store's earning rules and may issue points or rewards. Identify the customer by customer_id OR customer_email (exactly one). Pass distinct_id (e.g. an order number) to make it idempotent — a second activity with the same token + distinct_id is rejected. Custom activity types need Smile's Plus/Enterprise plan. Requires the activity:write scope. Smile: POST /activities.

Input parameters:

- `created_on_origin_at` (string): ISO 8601 date-time the action actually happened, if earlier than now.
- `customer_email` (string): Customer email (or give customer_id).
- `customer_id` (integer): Smile customer ID (or give customer_email).
- `distinct_id` (string): Unique id for this activity in your system; prevents duplicates for the same token.
- `token` (string, required): Activity type token, e.g. activity_f57a9b5a8d0ac5.

### `smile_purchase_points_product` (~171 tokens)

Redeem a customer's points for a reward

WRITE — SPENDS THE CUSTOMER'S POINTS: redeem points on the customer's behalf by purchasing a points product; Smile deducts the points and issues the reward (the response's points_purchase.reward_fulfillment usually holds a discount code). Only do this when the customer asked for it. For a 'variable' product pass points_to_spend; leave it out for 'fixed' products. There is no API to cancel a redemption — a mistaken one can only be compensated with smile_create_points_transaction. Requires the points_purchase:write scope. Smile: POST /points_products/{id}/purchase.

Input parameters:

- `customer_id` (integer, required): Smile customer ID.
- `points_product_id` (integer, required): Smile points product ID.
- `points_to_spend` (integer): Points to spend — variable-price products only.

## Diagnostics

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

## Score history

- 2026-10-03: 78
- 2026-10-02: 77
- 2026-10-01: 77
- 2026-09-30: 72
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/smile-io MCP server?

io.usefulapi/smile-io is an MCP server listed in the public MCP registry as io.usefulapi/smile-io. Look up loyalty customers, points history, rewards and VIP tiers, and add points or activities. This page covers its hosted endpoint (https://smile-io.usefulapi.io/mcp).

### Is the io.usefulapi/smile-io MCP server safe to use?

io.usefulapi/smile-io 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 io.usefulapi/smile-io MCP server expose?

io.usefulapi/smile-io exposes 14 tools: smile_list_customers, smile_get_customer, smile_list_points_transactions, smile_get_points_transaction, smile_list_points_products, and 9 more. Their descriptions and schemas cost roughly 1,731 tokens of context every time the server is loaded.

### Does the io.usefulapi/smile-io MCP server require authentication?

Yes. io.usefulapi/smile-io 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 io.usefulapi/smile-io MCP server still maintained?

io.usefulapi/smile-io is still listed as active in the MCP registry. We last reached this channel on 3 October 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://smile-io.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-smile-io/smile-io.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-smile-io/smile-io.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-smile-io/smile-io