Leal
REMOTE · MCP.GETLEAL.COM
Design and launch Apple Wallet and Google Wallet loyalty stamp cards for your shop, café or salon.
Available components
Last scanned (1 hour ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_store). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2873 tokens (~179/item across 16 items; 15 tools + 1 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 68
First indexed and scored.
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 5 Nov 2026 · Probed https://mcp.getleal.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getleal.com | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1f4a5da67e829f0ef25f71701c4d60 |
| SANs: getleal.com, *.getleal.com | ||||||
| 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 secure
Validation of mcp.getleal.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getleal.com. | present | 2371 | 13 | Verified |
| mcp.getleal.com. | Verified address RRset verified with the apex keys |
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=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.getleal.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.getleal.com/mcp | HTTPS enforced | 301 | https://mcp.getleal.com/mcp |
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 →
create_card Create a loyalty card ~713
Saves a loyalty card design and its rewards to a Leal store, ready for customers to add to Apple Wallet or Google Wallet. Takes the same design fields as preview_card_designs. Logos and strip photos are fetched from their URLs; if the store has no logo yet, the card's logo becomes the store logo. Needs a Leal account: the person is asked to sign in or create one.
| Name | Type | Req | Description |
|---|---|---|---|
| auxiliary_fields | array | – | Up to two extra front-of-pass fields, e.g. {label: "Perk", value: "10% off pastries"}. |
| card_color | string | – | Pass background colour, hex (#RRGGBB). |
| header_text | string | – | Text at the top of the pass. Defaults to the store name. Wallet apps truncate long headers, so keep it short. |
| initial_stamps | integer | – | Stamps a new customer starts with (a head start). Must be less than stamps_required. |
| logo_url | string | – | Public https URL of the wide logo shown top-left of the Apple pass (PNG, JPEG, WebP, GIF or SVG; transparent PNG works best). Ideally a version that reads on card_color. |
| name | string | yes | Internal name for the card, e.g. "Coffee card". Shown in Leal, not on the pass. |
| rewards | array | yes | Rewards customers can redeem, e.g. [{name: "Free coffee", stamps_required: 10}]. The free plan allows one reward per card. |
| show_member_field | boolean | – | Show the customer's name on the front of the pass. Default true. |
| show_stamps_to_reward_field | boolean | – | Show how many stamps until the next reward. Default true. |
| square_logo_url | string | – | Public https URL of a square logo or icon, used as the round logo on Google Wallet. |
| stamp_background_color | string | – | Fill colour of a collected stamp circle, hex. Empty stamp slots use a translucent version of it, so it should stand out from the strip. |
| stamp_color | string | – | Colour of the icon inside a collected stamp, hex. Must read clearly on stamp_background_color. |
| stamp_icon | string | – | Icon shown in each collected stamp. |
| stamps_required | integer | – | Stamps needed to fill the card. 6, 8 or 10 are common. |
| store_id | integer | – | Store id from list_stores. Optional when the login has one store. |
| strip_color | string | – | Strip colour, hex. Also shows behind preset and image strips when strip_opacity is below 100. |
| strip_image_url | string | – | Public https URL of a wide photo for the strip (strip_type image), e.g. a hero image from the brand's website. Cropped to 375×144. |
| strip_opacity | integer | – | Opacity of the strip colour or image over the card colour. 100 shows it exactly; 60–85 tints a photo with the card colour so stamps stand out. |
| strip_preset | string | – | Preset strip photo, used when strip_type is preset. |
| strip_type | string | – | Background of the stamp strip: a flat colour, one of Leal's preset photos, or an image from strip_image_url. |
| text_color | string | – | Colour of all text on the pass, hex. Must read clearly on card_color (4.5:1 contrast or better). |
No output schema declared.
No examples provided.
create_location Add a store location ~88
Adds a physical location to a store. The address is geocoded so wallet passes can remind customers nearby.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full street address including town and postcode. |
| name | string | yes | e.g. "Main Street" or the store name for a single shop. |
| store_id | integer | – | Store id from list_stores. Optional when the login has one store. |
No output schema declared.
No examples provided.
create_poster Create a signup poster ~203
Creates a printable poster with a QR code for a card. Customers scan it, fill in a short form on a public Leal signup page, and add the card to their wallet. Returns the signup link and a print link. Colours default to the card's.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | integer | yes | Card id from list_cards. |
| contact_collection_mode | string | – | What the signup form asks for. Default email_and_phone. |
| paper_size | string | – | Default a4. |
| primary_color | string | – | Poster background colour, hex. Defaults to the card colour. |
| require_birthday | boolean | – | Ask for a birthday (for birthday rewards). Default false. |
| secondary_color | string | – | Accent panel colour, hex. |
| text_color | string | – | Poster text colour, hex. Defaults to the card's text colour. |
| title | string | – | Headline, e.g. "Join our coffee club". Defaults to the card name. |
No output schema declared.
No examples provided.
create_reward Add a reward to a card ~96
Adds a reward that customers can redeem with stamps from a card, e.g. a free coffee at 10 stamps.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | integer | yes | Card id from list_cards. |
| description | string | – | Optional details, e.g. "Any size, any drink". |
| name | string | yes | What the customer gets, e.g. "Free coffee". |
| stamps_required | integer | yes | Stamps spent to redeem it. |
No output schema declared.
No examples provided.
create_store Create a store ~219
Adds a new, empty store to the login's agency, with its own cards, posters and locations: for a client, a second business, or a demo to show a prospect. Then set it up with create_card, create_poster and create_location using the returned store_id. Don't use this to set up a store the login already has: call list_stores first and use the existing store if it's the same business.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | integer | – | Agency id from list_stores. Only needed when this login runs several agencies. |
| logo_url | string | – | Public https URL of the wide logo (PNG, JPEG, WebP, GIF or SVG), e.g. from get_brand_kit. |
| name | string | yes | Store name in Leal, usually the business or client name, e.g. "Bean There Coffee". |
| square_logo_url | string | – | Public https URL of a square logo or icon. |
| store_name | string | – | Public name customers see on cards and signup pages, if different from name. |
No output schema declared.
No examples provided.
get_brand_kit Get brand kit from a website ~125
Reads a business's public website and returns its name, a colour palette (with where each colour was found; colours read from the logo are the most reliable, and website-builder default colours are filtered out), logo and icon image URLs, a hero image, a guess at the type of business, and a suggested starting card design built from those. Works without a Leal account. Use the result to propose card designs with preview_card_designs.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The business's website, e.g. https://beanthere.coffee or beanthere.coffee. |
No output schema declared.
No examples provided.
get_card Show a loyalty card ~39
Shows a saved loyalty card's design and rewards, with an Apple and Google Wallet preview.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | integer | yes | Card id from list_cards. |
No output schema declared.
No examples provided.
get_store_setup Get store setup ~66
Shows a store's setup checklist (store details, card, poster, first customer, staff app), plan limits and usage, and its cards with rewards, locations and posters.
| Name | Type | Req | Description |
|---|---|---|---|
| store_id | integer | – | Store id from list_stores. Optional when the login has one store. |
No output schema declared.
No examples provided.
list_cards List loyalty cards ~55
Lists a store's loyalty cards with their rewards.
| Name | Type | Req | Description |
|---|---|---|---|
| include_archived | boolean | – | Include archived cards. Default false. |
| store_id | integer | – | Store id from list_stores. Optional when the login has one store. |
No output schema declared.
No examples provided.
list_design_options List card design options ~49
Lists what a Leal loyalty card can look like: stamp icons, preset strip photos, limits, and how the pass is laid out on Apple and Google Wallet. Works without a Leal account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_stores List stores ~47
Lists the Leal stores this login can manage, with each store's id, plan and how far through setup it is, and the agencies it can add new stores to with create_store.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_card_designs Preview loyalty card designs ~104
Renders one to four loyalty card designs as Apple Wallet and Google Wallet passes so the person can compare them and pick one. Checks each design against Leal's rules and flags hard-to-read colour combinations. Returns a shareable preview link per design. Works without a Leal account; nothing is saved.
| Name | Type | Req | Description |
|---|---|---|---|
| designs | array | yes | The designs to show side by side. |
| store_name | string | – | The business name, shown where the pass shows the store. |
No output schema declared.
No examples provided.
update_card Update a loyalty card ~618
Changes a saved card's design. Only the fields passed change; the rest stay as they are. Customers' passes in Apple Wallet and Google Wallet update automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| auxiliary_fields | array | – | Up to two extra front-of-pass fields, e.g. {label: "Perk", value: "10% off pastries"}. |
| card_color | string | – | Pass background colour, hex (#RRGGBB). |
| card_id | integer | yes | Card id from list_cards. |
| header_text | string | – | Text at the top of the pass. Defaults to the store name. Wallet apps truncate long headers, so keep it short. |
| initial_stamps | integer | – | Stamps a new customer starts with (a head start). Must be less than stamps_required. |
| logo_url | string | – | Public https URL of the wide logo shown top-left of the Apple pass (PNG, JPEG, WebP, GIF or SVG; transparent PNG works best). Ideally a version that reads on card_color. |
| name | string | – | Internal name for the card, e.g. "Coffee card". Shown in Leal, not on the pass. |
| show_member_field | boolean | – | Show the customer's name on the front of the pass. Default true. |
| show_stamps_to_reward_field | boolean | – | Show how many stamps until the next reward. Default true. |
| square_logo_url | string | – | Public https URL of a square logo or icon, used as the round logo on Google Wallet. |
| stamp_background_color | string | – | Fill colour of a collected stamp circle, hex. Empty stamp slots use a translucent version of it, so it should stand out from the strip. |
| stamp_color | string | – | Colour of the icon inside a collected stamp, hex. Must read clearly on stamp_background_color. |
| stamp_icon | string | – | Icon shown in each collected stamp. |
| stamps_required | integer | – | Stamps needed to fill the card. 6, 8 or 10 are common. |
| strip_color | string | – | Strip colour, hex. Also shows behind preset and image strips when strip_opacity is below 100. |
| strip_image_url | string | – | Public https URL of a wide photo for the strip (strip_type image), e.g. a hero image from the brand's website. Cropped to 375×144. |
| strip_opacity | integer | – | Opacity of the strip colour or image over the card colour. 100 shows it exactly; 60–85 tints a photo with the card colour so stamps stand out. |
| strip_preset | string | – | Preset strip photo, used when strip_type is preset. |
| strip_type | string | – | Background of the stamp strip: a flat colour, one of Leal's preset photos, or an image from strip_image_url. |
| text_color | string | – | Colour of all text on the pass, hex. Must read clearly on card_color (4.5:1 contrast or better). |
No output schema declared.
No examples provided.
update_reward Update a reward ~84
Changes a reward's name, stamps needed or description, or turns it off. Only the fields passed change.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | false hides the reward from customers and staff. |
| description | string | – | – |
| name | string | – | – |
| reward_id | integer | yes | Reward id from list_cards or get_store_setup. |
| stamps_required | integer | – | – |
No output schema declared.
No examples provided.
update_store Update store name and logo ~130
Sets a store's public name and logos, which Leal uses on cards, posters and signup pages. Logos are fetched from public image URLs (PNG, JPEG, WebP, GIF or SVG). Replaces the current values.
| Name | Type | Req | Description |
|---|---|---|---|
| logo_url | string | – | Public https URL of the wide logo. |
| square_logo_url | string | – | Public https URL of a square logo or icon. |
| store_id | integer | – | Store id from list_stores. Optional when the login has one store. |
| store_name | string | – | The business name customers know, e.g. "Bean There Coffee". |
No output schema declared.
No examples provided.
How do I install the Leal MCP server?
Leal is a hosted endpoint at https://mcp.getleal.com/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 · mcp.getleal.com
claude mcp add --transport http com-getleal-leal 'https://mcp.getleal.com/mcp'
What is the Leal MCP server?
Leal is an MCP server listed in the public MCP registry as com.getleal/leal. Design and launch Apple Wallet and Google Wallet loyalty stamp cards for your shop, café or salon. This page covers its hosted endpoint (https://mcp.getleal.com/mcp).
Is the Leal MCP server safe to use?
Leal scores 72 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 Leal MCP server expose?
Leal exposes 15 tools: get_brand_kit, list_design_options, preview_card_designs, list_stores, get_store_setup, and 10 more. Their descriptions and schemas cost roughly 2,636 tokens of context every time the server is loaded.
Does the Leal MCP server require authentication?
No. We connected to Leal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Leal MCP server still maintained?
Leal is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.