Smile.io MCP by usefulapi
io.usefulapi/smile-iousefulapi.iostreamable-httpv1.40.4Scanned
Look up loyalty customers, points history, rewards and VIP tiers, and add points or activities.
14 tools: 3 can delete or cancel things and 11 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Smile.io MCP by usefulapi can do
The Smile.io MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (3 tools: smile_create_points_transaction, smile_create_activity and smile_purchase_points_product). 11 tools only read.
1 tool reads private data (smile_get_customer); 1 tool brings in text other people can write (smile_get_customer).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Deletes or cancels 3Claude Code: deny
smile_create_activityWRITE: record that a customer performed an action (identified by an activity type token configured in Smile Admin, e.g.No findings
Why it is in this group
- The name "smile_create_activity" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Record a customer activity
- destructiveHint: true
smile_create_points_transactionWRITE: add or deduct points from a customer's balance (a manual adjustment, e.g.No findings
Why it is in this group
- The name "smile_create_points_transaction" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Adjust a customer's points balance
- destructiveHint: true
smile_purchase_points_productWRITE — 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_p…No findings
Why it is in this group
- The name "smile_purchase_points_product" says "purchase": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Redeem a customer's points for a reward
- destructiveHint: true
Only reads 11Show 11 read-only tools
smile_get_customerFetch 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.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "smile_get_customer" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get a customer
- readOnlyHint: true
smile_get_points_productFetch one points product (a way to redeem points) by ID, including its reward.No findings
Why it is in this group
- The name "smile_get_points_product" says "get": a word for reading.
Description, as the server wrote it Fetch one points product (a way to redeem points) by ID, including its reward. Smile: GET /points_products/{id}.
Annotations the server declares
- title: Get a points product
- readOnlyHint: true
smile_get_points_settingsFetch the points program's configuration, e.g.No findings
Why it is in this group
- The name "smile_get_points_settings" says "get": a word for reading.
Description, as the server wrote it Fetch the points program's configuration, e.g. the points currency label ("Points", "Stars"). Smile: GET /points_settings.
Annotations the server declares
- title: Get points settings
- readOnlyHint: true
smile_get_points_transactionFetch one points transaction by ID.No findings
Why it is in this group
- The name "smile_get_points_transaction" says "get": a word for reading.
Description, as the server wrote it Fetch one points transaction by ID. Smile: GET /points_transactions/{id}.
Annotations the server declares
- title: Get a points transaction
- readOnlyHint: true
smile_get_referral_settingsFetch the referral program's configuration: whether it is active, and the sender (advocate) and receiver (friend) rewards.No findings
Why it is in this group
- The name "smile_get_referral_settings" says "get": a word for reading.
Description, as the server wrote it Fetch the referral program's configuration: whether it is active, and the sender (advocate) and receiver (friend) rewards. Smile: GET /referral_settings.
Annotations the server declares
- title: Get referral settings
- readOnlyHint: true
smile_list_customersList loyalty-program customers, newest first, with their points balance, state and VIP tier id.No findings
Why it is in this group
- The name "smile_list_customers" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List customers
- readOnlyHint: true
smile_list_earning_rulesList 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 an…No findings
Why it is in this group
- The name "smile_list_earning_rules" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List earning rules
- readOnlyHint: true
smile_list_points_productsList points products — the rewards customers can buy with points.No findings
Why it is in this group
- The name "smile_list_points_products" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List points products
- readOnlyHint: true
smile_list_points_transactionsList points transactions (every earn, spend and manual adjustment), newest first — e.g.No findings
Why it is in this group
- The name "smile_list_points_transactions" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List points transactions
- readOnlyHint: true
smile_list_reward_fulfillmentsList rewards that have been issued to customers — usually discount codes — with code, fulfillment_status (pending/issued/cancelled/failed), usage_status (used/unused/untracked), us…No findings
Why it is in this group
- The name "smile_list_reward_fulfillments" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List reward fulfillments
- readOnlyHint: true
smile_list_vip_tiersList the VIP program's tiers, sorted by milestone (the threshold to reach each tier), optionally with each tier's perks and entry rewards.No findings
Why it is in this group
- The name "smile_list_vip_tiers" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List VIP tiers
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:38 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://smile-io.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://smile-io.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://smile-io.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://smile-io.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http smile-io https://smile-io.usefulapi.io/mcpclaude mcp add --transport http smile-io https://smile-io.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__smile-io__smile_list_customers",
"mcp__smile-io__smile_get_customer",
"mcp__smile-io__smile_list_points_transactions",
"mcp__smile-io__smile_get_points_transaction",
"mcp__smile-io__smile_list_points_products",
"mcp__smile-io__smile_get_points_product",
"mcp__smile-io__smile_list_reward_fulfillments",
"mcp__smile-io__smile_list_earning_rules",
"mcp__smile-io__smile_list_vip_tiers",
"mcp__smile-io__smile_get_points_settings",
"mcp__smile-io__smile_get_referral_settings"
],
"ask": [],
"deny": [
"mcp__smile-io__smile_create_points_transaction",
"mcp__smile-io__smile_create_activity",
"mcp__smile-io__smile_purchase_points_product"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as smile-io. Review it before you use it.
Capability tags behind 1 rule
- mcp__smile-io__smile_get_customer private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/smile-io/verify?hash=dc7ec61a62663877ee943a993e4bf1cf9ac08773d1c1b9d1623e7c1f51562a6e" | jq -e '.changed == false'Pinned hash dc7ec61a6266, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/smile-io/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/smile-io)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Smile.io MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Smile.io MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 14 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Smile.io MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: smile_create_points_transaction, smile_create_activity and smile_purchase_points_product.
Can the Smile.io MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Smile.io MCP by usefulapi have?
- 14 tools: 3 destructive, 11 read. smile_create_points_transaction, smile_create_activity, smile_purchase_points_product, smile_list_customers, smile_get_customer, smile_list_points_transactions, smile_get_points_transaction, smile_list_points_products and 6 more.
Does the Smile.io MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Smile.io MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Smile.io MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.