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.

Loyal Spark

REMOTE · API.LOYALSPARK.ONLINE

43 MCP tools for onchain loyalty on Base: programs, minting, rewards, vouchers. x402 or lsk_ key.

0 this week 77 Trust /100

Last scanned (18 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (23 Oct 2026). See the changelog before you install this server.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4566 tokens (~106/item across 43 items; 43 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 Management93
  • Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 2 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
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 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 44 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 93% → 100% ▲ functional
    • Server version: 1.0.0 → 1.0.5 functional
    • “create_loyalty_program” reworded the description of “locale” cosmetic
    • “create_loyalty_program” reworded the description of “preferred_style” cosmetic
    • “create_loyalty_program” reworded the description of “target_audience” cosmetic
    • “generate_program_defaults” reworded the description of “business_name” cosmetic
    • “generate_program_defaults” reworded the description of “category” cosmetic
    • “generate_program_defaults” reworded the description of “description” cosmetic
    • “generate_program_defaults” reworded the description of “locale” cosmetic
    • “generate_program_defaults” reworded the description of “preferred_style” cosmetic
    • “generate_program_defaults” reworded the description of “target_audience” cosmetic
    • Tool “activate_loyalty_program” changed its title: Activate Loyalty Program cosmetic
    • Tool “bazaar_discover_mcp_servers” changed its title: Bazaar Discover MCP Servers cosmetic
    • Tool “bazaar_discover_resources” changed its title: Bazaar Discover Resources cosmetic
    • Tool “bazaar_pay_and_call” changed its title: Bazaar Pay And Call cosmetic
    • Tool “bazaar_probe_x402” changed its title: Bazaar Probe x402 cosmetic
    • Tool “check_voucher_status” changed its title: Check Voucher Status cosmetic
    • Tool “confirm_mint_fee” changed its title: Confirm Mint Fee cosmetic
    • Tool “create_gift_certificate” changed its title: Create Gift Certificate cosmetic
    • Tool “create_loyalty_program” changed its title: Create Loyalty Program cosmetic
    • Tool “create_personalized_offer” changed its title: Create Personalized Offer cosmetic
    • Tool “create_reward” changed its title: Create Reward cosmetic
    • Tool “delete_report” changed its title: Delete Report cosmetic
    • Tool “earn_points” changed its title: Earn Points cosmetic
    • Tool “export_customers” changed its title: Export Customers cosmetic
    • Tool “generate_program_defaults” changed its title: Generate Program Defaults cosmetic
    • Tool “get_my_profile” changed its title: Get My Profile cosmetic
    • Tool “get_payment_info” changed its title: Get Payment Info cosmetic
    • Tool “get_platform_info” changed its title: Get Platform Info cosmetic
    • Tool “get_program_analytics” changed its title: Get Program Analytics cosmetic
    • Tool “get_program_workflow_status” changed its title: Get Program Workflow Status cosmetic
    • Tool “get_token_balance” changed its title: Get Token Balance cosmetic
    • Tool “list_fee_obligations” changed its title: List Fee Obligations cosmetic
    • Tool “list_gift_certificates” changed its title: List Gift Certificates cosmetic
    • Tool “list_loyalty_programs” changed its title: List Loyalty Programs cosmetic
    • Tool “list_marketplace_offers” changed its title: List Marketplace Offers cosmetic
    • Tool “list_mints” changed its title: List Mints cosmetic
    • Tool “list_my_reports” changed its title: List My Reports cosmetic
    • Tool “list_rewards” changed its title: List Rewards cosmetic
    • Tool “list_store_discount_codes” changed its title: List Store Discount Codes cosmetic
    • Tool “mark_gift_certificate_minted” changed its title: Mark Gift Certificate Minted cosmetic
    • Tool “mint_loyalty_tokens” changed its title: Mint Loyalty Tokens cosmetic
    • Tool “redeem_reward” changed its title: Redeem Reward cosmetic
    • Tool “register_loyalty_program” changed its title: Register Loyalty Program cosmetic
    • Tool “revoke_gift_certificate” changed its title: Revoke Gift Certificate cosmetic
    • Tool “send_report” changed its title: Send Report cosmetic
    • Tool “set_store_sales_channel” changed its title: Set Store Sales Channel cosmetic
    • Tool “transfer_loyalty_tokens” changed its title: Transfer Loyalty Tokens cosmetic
    • Tool “update_program_config” changed its title: Update Program Config cosmetic
    • Tool “update_program_status” changed its title: Update Program Status cosmetic
    • Tool “update_report_status” changed its title: Update Report Status cosmetic
    • Tool “update_reward_status” changed its title: Update Reward Status cosmetic
    • Tool “update_store_discount_code” changed its title: Update Store Discount Code cosmetic
    • Tool “use_voucher” changed its title: Use Voucher cosmetic
  • 10 Nov 26 0
    • Tool “get_my_profile” rewrote its description, which is the text the model reads security
    • New tool “get_payment_info” functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 0
    • Tool “earn_points” rewrote its description, which is the text the model reads security
    • Tool “mint_loyalty_tokens” rewrote its description, which is the text the model reads security
    • Tool “use_voucher” rewrote its description, which is the text the model reads security
    • “confirm_mint_fee” added an optional parameter “mint_intent_id” cosmetic
    • “use_voucher” added an optional parameter “code” cosmetic
  • 2 Nov 26 0
    • Tool “export_customers” rewrote its description, which is the text the model reads security
    • Tool “get_program_analytics” rewrote its description, which is the text the model reads security
    • Tool “list_mints” rewrote its description, which is the text the model reads security
    • Tool “transfer_loyalty_tokens” rewrote its description, which is the text the model reads security
    • “transfer_loyalty_tokens” added an optional parameter “to_address” cosmetic
    • “send_report” reworded the description of “report_type” cosmetic
    • “transfer_loyalty_tokens” made “to” optional cosmetic
  • 31 Oct 26 0
    • Tool “bazaar_discover_mcp_servers” rewrote its description, which is the text the model reads security
    • Tool “bazaar_probe_x402” rewrote its description, which is the text the model reads security
    • “bazaar_discover_mcp_servers” reworded the description of “cursor” cosmetic
    • “bazaar_discover_mcp_servers” reworded the description of “limit” cosmetic
    • “bazaar_discover_mcp_servers” reworded the description of “network” cosmetic
    • “bazaar_discover_mcp_servers” reworded the description of “q” cosmetic
  • 29 Oct 26 0
    • Tool “earn_points” rewrote its description, which is the text the model reads security
    • “earn_points” added an optional parameter “customer_email” cosmetic
    • “earn_points” added an optional parameter “points_to_redeem” cosmetic
    • “earn_points” added an optional parameter “redeem_all” cosmetic
    • “earn_points” reworded the description of “customer_address” cosmetic
  • 28 Oct 26 0
    • Tool “get_token_balance” rewrote its description, which is the text the model reads security
    • Tool “mint_loyalty_tokens” rewrote its description, which is the text the model reads security
    • “mint_loyalty_tokens” added an optional parameter “recipient_email” cosmetic
    • “get_token_balance” reworded the description of “customer_address” cosmetic
    • “mint_loyalty_tokens” reworded the description of “recipient” cosmetic
    • “mint_loyalty_tokens” reworded the description of “recipient_address” cosmetic
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 21 Nov 2026 · Probed https://api.loyalspark.online/loyalty-mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=loyalspark.online CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 aae4d9a8eed2dbb00e0250793243cdb5
SANs: loyalspark.online, api.loyalspark.online, *.api.loyalspark.online
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 api.loyalspark.online. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
online. DS published 30961 13 Verified
loyalspark.online. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.loyalspark.online/loyalty-mcp Verified 200
http (plaintext) http://api.loyalspark.online/loyalty-mcp HTTPS enforced 308 https://api.loyalspark.online/loyalty-mcp
MCP tools · 43 exposed · ~4,423 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
activate_loyalty_program ~53

For legacy ERC-20 programs: returns unpauseUtility + enableMinting calldata. For B20 programs: no-op (already active).

NameTypeReqDescription
token_addressstringyesToken contract address (0x...)

No output schema declared.

No examples provided.

bazaar_discover_mcp_servers ~145

Search Coinbase CDP's Bazaar MCP catalog (search_resources) for third-party x402-payable tools. Read-only, free. Rows are run via the Bazaar MCP server's proxy_tool_call, not here.

NameTypeReqDescription
cursorstring–Ignored: CDP search has no cursor. Narrow with q/network.
limitnumber–Max rows (default 20, max 20)
networkstring–Network: 'base', 'base-sepolia', or CAIP-2 like 'eip155:8453'
qstring–Search text, e.g. 'weather' or 'loyalty'

No output schema declared.

No examples provided.

bazaar_discover_resources ~128

Discover third-party x402-paid resources published in Coinbase CDP's Bazaar (docs, data feeds, AI inference, etc). Read-only. Filter by free-text q and/or network (e.g. 'base').

NameTypeReqDescription
cursorstring–Pagination cursor from a previous call
limitnumber–Max rows returned (default 25, max 100)
networkstring–Filter by network, e.g. 'base' or 'base-sepolia'
qstring–Free-text filter matched against the resource JSON (name/description/url)

No output schema declared.

No examples provided.

bazaar_pay_and_call ~212

Pay a Loyal Spark x402 URL on api.loyalspark.online with the merchant agent's CDP MPC wallet (EIP-3009 exact scheme, Base USDC). Other hosts are refused before any signature. Requires scope 'mint' and an active CDP wallet. max_usdc default 0.25, hard limit 10.

NameTypeReqDescription
allowed_networksarray–Networks to accept (default ['base', 'eip155:8453'])
allowed_schemesarray–x402 schemes to accept (default ['exact'])
body––Optional JSON request body for non-GET methods
headersobject–Extra request headers (Accept/Content-Type auto-set)
max_usdcnumber–Spend cap for THIS call in USDC (default 0.25, must be ≤ 10)
methodstring–HTTP method (default GET)
urlstringyesFull https:// URL of the x402 resource

No output schema declared.

No examples provided.

bazaar_probe_x402 ~135

Probe one x402 resource URL without paying: a single GET (https only, 5 s, 64 KB, no redirects). If it answers HTTP 402, returns a parsed summary of the x402 payment requirements (PAYMENT-REQUIRED header or accepts[]). Any other status returns error not_x402_resource with the status only: the response body is never returned. No signing. No API key needed: keyless calls are limited to 20/minute per IP; with a key the key's own limits apply.

NameTypeReqDescription
urlstringyesFull https:// URL of the x402-paid endpoint

No output schema declared.

No examples provided.

check_voucher_status ~143

Check voucher status for this merchant. Send one of code, voucher_code, or voucher_id (anyOf). If none is sent the tool returns error_code missing_identifier, an example, and next_action. Anonymous public lookup is GET /agent-api/vouchers/status.

NameTypeReqDescription
codestring–Voucher code (LOYAL-XXXX-XXXX-XXXX-XXXX). One of code, voucher_code, or voucher_id is required.
voucher_codestring–Alias of code. One of code, voucher_code, or voucher_id is required.
voucher_idstring–Voucher UUID. One of code, voucher_code, or voucher_id is required.

No output schema declared.

No examples provided.

confirm_mint_fee ~201

Confirm a prepared mint on Base. Verifies the protocol-fee mint and, when recipient_tx_hash is set (or the fee receipt already contains the recipient mint), writes customer_tier_status so get_token_balance leaves 0. Same hash for both fields when EIP-5792 batched the calls. A second call with recipient_tx_hash still credits the customer after the fee is already settled.

NameTypeReqDescription
fee_tx_hashstringyesTransaction hash of the protocol fee mint
mint_intent_idstring–Optional mint_intent_id from the mint response; links this exact intent when several pending mints share token, recipient and amount.
obligation_idstringyesfee_obligation_id returned by mint_loyalty_tokens or earn_points
recipient_tx_hashstring–Transaction hash of the mint to the recipient. Same as fee_tx_hash when both mints are in one transaction. Required to update GET /balance.

No output schema declared.

No examples provided.

create_gift_certificate ~259

Create a gift / welcome certificate (UDS-style) with a unique random redemption code (LOYAL-XXXX-XXXX-XXXX). Customer redeems via QR or by entering the code; merchant then mints tokens on-chain. Use for welcome bonuses, promo campaigns, partnership gifts.

NameTypeReqDescription
descriptionstring–Optional descriptive text shown to the customer
expires_in_daysnumber–Validity period in days (omit for no expiry)
image_urlstring–Optional public image URL for the cert design
max_redemption_percentnumber–Max % of any future purchase the customer can pay with these tokens (5–100). Default 50.
points_per_dollarnumber–Optional override of program rate (e.g. 10 = 10 tokens per $1). Defaults to program's points_per_dollar.
quantitynumber–Number of certificates to create as a batch (1–100, default 1)
titlestring–Display title (default: 'Gift Certificate')
token_addressstringyesERC-20 loyalty token address (must belong to the agent's merchant)
usd_amountnumberyesCertificate face value in USD (positive)

No output schema declared.

No examples provided.

create_loyalty_program ~347

Get factory calldata to deploy a new loyalty token on Base. Defaults to B20 (Base-native B20 asset standard, ERC-20 compatible, single tx, active immediately). Pass token_standard='erc20' for the legacy factory. For B20, MINT_ROLE is granted atomically to the merchant admin AND to the agent's CDP wallet (or explicit extra_minters) so autonomous agents can mint with no follow-up transaction.

NameTypeReqDescription
agent_wallet_addressstring–(B20 only) Additional wallet to grant MINT_ROLE atomically. Defaults to the agent's active CDP MPC wallet if not provided.
auto_generateboolean–Internal automation only — fills missing name/symbol from examples. External agents should pass explicit name and symbol.
business_contextobject–Optional context for examples only
expiration_daysnumber–Program duration in days (default: 365)
extra_mintersarray–(B20 only) Extra addresses to grant MINT_ROLE atomically in the same deploy tx.
localestring–Optional locale/language hint for auto_generate examples
namestringyesProgram name (required for external agents)
preferred_stylestring–Optional naming style hint when auto_generate fills examples
symbolstringyesToken symbol, 2-5 chars (required for external agents)
target_audiencestring–Optional audience hint for auto_generate examples
token_standardstring–'b20' (default, single-tx deploy on Base precompile factory) or 'erc20' (legacy factory, requires activate_loyalty_program follow-up)

No output schema declared.

No examples provided.

create_personalized_offer ~136

Create a personalized offer for a specific customer. Use when analytics reveal engagement patterns (e.g., inactive customers, high-value segments).

NameTypeReqDescription
bonus_tokensnumber–Bonus tokens to award
customer_addressstringyesCustomer wallet address
descriptionstring–Offer description
discount_percentagenumber–Discount percentage (0-100)
titlestringyesOffer title (e.g., 'Welcome back! 20% bonus tokens')
token_addressstringyesToken contract address
valid_daysnumber–How many days the offer is valid (default: 7)

No output schema declared.

No examples provided.

create_reward ~58

Create a new reward redeemable with loyalty tokens

NameTypeReqDescription
costnumberyesToken cost to redeem
descriptionstring–Reward description
namestringyesReward name
token_addressstringyesToken contract address

No output schema declared.

No examples provided.

delete_report ~30

Internal. Delete a report you submitted.

NameTypeReqDescription
report_idstringyesUUID of the report to delete

No output schema declared.

No examples provided.

earn_points ~231

Mint cashback tokens for a purchase at the program's cashback rate, optionally redeeming points first (points_to_redeem or redeem_all) to lower the payable amount. Returns a fee-first calls[] bundle (protocol fee mint, then the customer mint): submit in order (atomically via EIP-5792 if supported), then call confirm_mint_fee with obligation_id, fee_tx_hash, recipient_tx_hash. Unconfirmed fees block future mints.

NameTypeReqDescription
cashback_ratenumber–Override cashback rate (%). If omitted, uses the program's default rate.
customer_addressstringyesCustomer wallet (0x...) or email address
customer_emailstring–Customer email address
points_to_redeemnumber–Optional integer loyalty points to redeem at the counter to reduce purchase_amount.
purchase_amountnumberyesPurchase amount in currency units (e.g. dollars)
redeem_allboolean–If true, redeems all available customer loyalty points (up to purchase_amount when positive).
token_addressstringyesToken contract address (0x...)

No output schema declared.

No examples provided.

export_customers ~90

Export customers of one of your loyalty programs: the same wallet set and total_customers as GET /customers and get_program_analytics (voucher holders, ledger rows, completed mints), each with voucher stats, on-chain current_balance plus offchain_ledger_balance, and tier. Email-only store customers are listed in store_customers.

NameTypeReqDescription
token_addressstringyesToken address of the loyalty program

No output schema declared.

No examples provided.

generate_program_defaults ~149

Workflow planner: field catalog, required parameters, next_actions, and non-binding examples. External agents must choose their own name, symbol, and economics.

NameTypeReqDescription
business_namestring–Optional merchant / brand name for example suggestions
categorystring–Optional business category (e.g. cafe, retail)
descriptionstring–Optional short business description for examples
localestring–Optional locale/language hint for example names (e.g. en, ru)
preferred_stylestring–Optional naming style hint for examples (e.g. playful, premium)
target_audiencestring–Optional audience hint for examples (e.g. locals, tourists)

No output schema declared.

No examples provided.

get_my_profile ~23

Get authenticated agent's profile, plan limits, and current-period usage

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_payment_info ~81

Free: agent Pro/Enterprise (or merchant) plan options, USDC subscription wallet, per-plan limits, annual prices, and the required-sender rule. Optional product=agent|merchant. Prefer this before paying; verify with POST /verify-agent-plan-payment action verify_payment.

NameTypeReqDescription
productstring–"agent" (default) or "merchant"

No output schema declared.

No examples provided.

get_platform_info ~20

Get info about Loyal Spark protocol on Base L2

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_program_analytics ~60

Get analytics for one of your loyalty programs. total_customers is the same count export_customers and GET /customers report; a program you do not own returns program_not_found.

NameTypeReqDescription
token_addressstringyesToken contract address (0x...)

No output schema declared.

No examples provided.

get_program_workflow_status ~46

Explain the next merchant action: current_step, required fields, and ordered next_actions (you provide all parameter values)

NameTypeReqDescription
token_addressstring–Optional token to inspect

No output schema declared.

No examples provided.

get_token_balance ~67

Get loyalty token balance and tier info for a customer (accepts 0x Base wallet address or customer email in customer_address / customer_email)

NameTypeReqDescription
customer_addressstringyesCustomer 0x Base wallet address or customer email
token_addressstringyesToken contract address

No output schema declared.

No examples provided.

list_fee_obligations ~59

List protocol-fee obligations for this API key. status=unpaid is an alias for pending. Each unpaid row includes next_action describing POST /mint/confirm.

NameTypeReqDescription
statusstring–unpaid, pending, settled, or failed

No output schema declared.

No examples provided.

list_gift_certificates ~81

List gift certificates issued by the agent's merchant (with status and redemption info).

NameTypeReqDescription
limitnumber–Max rows (default 50, max 200)
statusstring–Filter by status: active, pending_mint, redeemed, expired, revoked
token_addressstring–Filter by program token address (optional)

No output schema declared.

No examples provided.

list_loyalty_programs ~34

List loyalty programs owned by the agent's merchant

NameTypeReqDescription
include_expiredboolean–Include expired programs

No output schema declared.

No examples provided.

list_marketplace_offers ~70

List active token trading offers on the marketplace

NameTypeReqDescription
limitnumber–Max results (1-100)
statusstring–Filter: active/completed/cancelled
token_addressstring–Optional. When set, only offers that give or ask for this token.

No output schema declared.

No examples provided.

list_mints ~78

List mint intents for this merchant. status=pending means transaction_hash is still null (confirm has not credited the recipient). status=completed means the recipient mint was recorded. GET /balance offchain_ledger_balance stays 0 until confirm.

NameTypeReqDescription
statusstring–pending or completed
token_addressstring–Optional loyalty token

No output schema declared.

No examples provided.

list_my_reports ~61

Internal. List reports this agent submitted (status new, reviewed, or done).

NameTypeReqDescription
limitnumber–Max results 1-50 (default: 20)
statusstring–Filter by status: new, reviewed, done (optional)

No output schema declared.

No examples provided.

list_rewards ~53

List rewards for a loyalty program by token_address. Includes redemption metrics (total vouchers issued, redeemed, and last-30-day counts) for each reward.

NameTypeReqDescription
token_addressstringyesToken contract address (0x...)

No output schema declared.

No examples provided.

list_store_discount_codes ~53

List discount codes for this merchant's Shopify store, plus how customers spend points (online code, register voucher, or both).

NameTypeReqDescription
token_addressstring–Program address. Omit to list every linked store.

No output schema declared.

No examples provided.

mark_gift_certificate_minted ~78

After the merchant submits the on-chain mint transaction for a claimed gift certificate, call this to mark it as minted (status pending_mint -> redeemed) and store the mint tx hash.

NameTypeReqDescription
certificate_idstringyesUUID of the certificate
transaction_hashstringyesBase L2 mint transaction hash (0x...)

No output schema declared.

No examples provided.

mint_loyalty_tokens ~196

Record a mint intent and get a fee-first calls[] bundle: protocol fee mint first (in the merchant's own loyalty tokens, not USDC), then the recipient mint. Submit both in order (atomically via EIP-5792 if supported), then call confirm_mint_fee with obligation_id, fee_tx_hash, recipient_tx_hash. Unconfirmed fees block future mints. recipient_address takes a 0x Base wallet or a customer email (or use recipient_email); the wallet is resolved server-side.

NameTypeReqDescription
amountnumberyesTokens to mint
recipientstring–Legacy alias for recipient_address (0x address or email)
recipient_addressstring–Customer 0x Base wallet address or customer email receiving minted tokens. Preferred — matches REST.
recipient_emailstring–Customer email address to resolve to their Base wallet
token_addressstringyesToken contract address

No output schema declared.

No examples provided.

redeem_reward ~78

Redeem a reward by providing a verified token transfer transaction hash. Creates a voucher for the customer.

NameTypeReqDescription
customer_addressstringyesWallet address of the customer who transferred tokens
reward_idstringyesUUID of the reward to redeem
transaction_hashstringyesOnchain tx hash of the token transfer from customer to merchant

No output schema declared.

No examples provided.

register_loyalty_program ~167

Register a deployed token as a loyalty program in the database. B20 tokens are registered as active; legacy ERC-20 as inactive (activate next).

NameTypeReqDescription
cashback_ratenumber–Default cashback percent for earn (1–100). Omit for DB default (5).
expiration_daysnumber–Duration in days (default: 365)
namestringyesProgram name
points_per_dollarnumber–Loyalty points per $1 spent (1–1000). Omit for DB default (1).
symbolstringyesToken symbol
token_addressstringyesDeployed token contract address (0x...)
token_standardstring–'b20' (default) or 'erc20' (legacy)

No output schema declared.

No examples provided.

revoke_gift_certificate ~63

Revoke an active gift certificate (status active -> revoked). Only the issuing merchant can revoke. Already-redeemed/minted certificates cannot be revoked.

NameTypeReqDescription
certificate_idstringyesUUID of the certificate from create_gift_certificate / list_gift_certificates

No output schema declared.

No examples provided.

send_report ~161

Internal. Send a report to the merchant's Agent Reports dashboard (SEO audits, growth ideas, anomalies, weekly summaries). Not a loyalty action.

NameTypeReqDescription
action_itemsarray–List of suggested action items
agent_rolestringyesYour role: ceo, seo, growth, or analyst
contentstringyesReport body text (max 10000 chars)
prioritystring–Priority: low, medium, high, or critical
report_typestringyesOne of: seo_audit, audit, growth_idea, data_report, anomaly, task, recommendation, weekly_report. Anything else is rejected (400 invalid_input), not renamed.
titlestringyesReport title (max 500 chars)

No output schema declared.

No examples provided.

set_store_sales_channel ~52

Set how this store's customers spend loyalty points: online (checkout code), offline (voucher at the register), or both (the shopper chooses).

NameTypeReqDescription
channelstringyesonline, offline, or both

No output schema declared.

No examples provided.

transfer_loyalty_tokens ~102

Build B20 token transfer calldata (ERC-20 compatible) to send loyalty tokens from your merchant wallet to any 0x address. Recipient: to (alias to_address).

NameTypeReqDescription
amountnumberyesTokens to transfer
tostring–Recipient wallet (0x...)
to_addressstring–Alias for to (same as REST POST /transfer to_address)
token_addressstringyesToken contract address (0x...)

No output schema declared.

No examples provided.

update_program_config ~97

Update default cashback_rate and/or points_per_dollar for a program (same as merchant dashboard sliders)

NameTypeReqDescription
cashback_ratenumber–New default cashback % for earn (1–100). Omit to leave unchanged.
points_per_dollarnumber–New points per $1 (0–1000, exclusive 0). Omit to leave unchanged.
token_addressstringyesToken contract address (0x...)

No output schema declared.

No examples provided.

update_program_status ~48

Update program status in database after onchain activation/pause

NameTypeReqDescription
statusstringyesNew status: active, paused, or inactive
token_addressstringyesToken contract address

No output schema declared.

No examples provided.

update_report_status ~46

Internal. Set a report you submitted to reviewed or done.

NameTypeReqDescription
report_idstringyesUUID of the report
statusstringyesNew status: reviewed or done

No output schema declared.

No examples provided.

update_reward_status ~54

Activate or deactivate a reward in the catalog. Use to manage reward availability based on analytics.

NameTypeReqDescription
is_activebooleanyestrue to activate, false to deactivate
reward_idstringyesUUID of the reward

No output schema declared.

No examples provided.

update_store_discount_code ~59

Mark a Shopify discount code used, or cancel it and return the loyalty points. Same actions as the merchant discount-code journal.

NameTypeReqDescription
actionstringyesuse or cancel
redemption_idstringyesId from list_store_discount_codes.

No output schema declared.

No examples provided.

use_voucher ~119

Mark a voucher as used at the merchant. Send one of voucher_code (alias code) or voucher_id (anyOf). If neither is sent the tool returns error_code missing_identifier and an example. A voucher used before returns error_code voucher_already_used (do not retry).

NameTypeReqDescription
codestring–Alias of voucher_code.
voucher_codestring–Voucher code (LOYAL-XXXX-XXXX-XXXX-XXXX). Use this OR voucher_id.
voucher_idstring–Voucher UUID. Use this OR voucher_code.

No output schema declared.

No examples provided.

Install

How do I install the Loyal Spark MCP server?

Loyal Spark is a hosted endpoint at https://api.loyalspark.online/loyalty-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 · api.loyalspark.online

# add to Claude Code
claude mcp add --transport http aspekt19-loyal-spark 'https://api.loyalspark.online/loyalty-mcp'
Common questions

What is the Loyal Spark MCP server?

Loyal Spark is an MCP server listed in the public MCP registry as io.github.aspekt19/loyal-spark. 43 MCP tools for onchain loyalty on Base: programs, minting, rewards, vouchers. x402 or lsk_ key. This page covers its hosted endpoint (https://api.loyalspark.online/loyalty-mcp).

Is the Loyal Spark MCP server safe to use?

Loyal Spark scores 77 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 Loyal Spark MCP server expose?

Loyal Spark exposes 43 tools: get_platform_info, get_my_profile, get_payment_info, generate_program_defaults, get_program_workflow_status, and 38 more. Their descriptions and schemas cost roughly 4,423 tokens of context every time the server is loaded.

Does the Loyal Spark MCP server require authentication?

No. We connected to Loyal Spark without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Loyal Spark MCP server still maintained?

Loyal Spark is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Loyal Spark MCP server?

VerifyMCP ran 13 checks on Loyal Spark, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.