Loyal Spark Loyalty Protocol
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_platform_infoB | Get info about Loyal Spark protocol on Base L2 |
| get_my_profileB | Get authenticated agent's profile |
| list_loyalty_programsB | List loyalty programs owned by the agent's merchant |
| create_loyalty_programA | Get factory calldata to deploy a new ERC-20 loyalty token on Base |
| register_loyalty_programC | Register a deployed token as a loyalty program in the database |
| activate_loyalty_programA | Get activation calldata (unpauseUtility + enableMinting) for an inactive program |
| update_program_statusA | Update program status in database after on-chain activation/pause |
| list_rewardsC | List rewards for a loyalty program by token_address |
| create_rewardC | Create a new reward redeemable with loyalty tokens |
| mint_loyalty_tokensB | Record mint intent and get smart contract call params |
| transfer_loyalty_tokensC | Get calldata to transfer loyalty tokens between wallets |
| get_token_balanceB | Get loyalty token balance and tier info for a customer |
| get_program_analyticsB | Get analytics for your loyalty programs |
| list_marketplace_offersC | List active token trading offers on the marketplace |
| redeem_rewardA | Redeem a reward by providing a verified token transfer transaction hash. Creates a voucher for the customer. |
| use_voucherA | Mark a voucher as used (redeemed by customer at merchant). Merchant-only operation. |
| check_voucher_statusA | Check voucher status by code or ID. Public endpoint — no API key or authentication required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aspekt19/unboxed-loyalty-spark'
If you have feedback or need assistance with the MCP directory API, please join our Discord server