mcp-registry/io.github.aspekt19/loyal-spark · v1.0.0
As of 2026-10-20 15:25 UTC, the Aspekt19 Loyal Spark MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 4 minutes.
Base MCP (39 tools) on Base: programs, mint, rewards. lsk_ key; plan limits enforced. /for-agents
Claude Code
claude mcp add --transport http aspekt19-loyal-spark-mcp-server https://api.loyalspark.online/loyalty-mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"aspekt19-loyal-spark-mcp-server": {
"type": "http",
"url": "https://api.loyalspark.online/loyalty-mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
42 of 42 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
42 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
13 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
9 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Handshake + tools/list takes ~1,989 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.aspekt19%2Floyal-spark/fixes
{
"name": "bazaar_pay_and_call",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Full https:// URL of the x402 resource"
},
"body": {
"description": "Optional JSON request body for non-GET methods",
"type": "string"
},
"method": {
"enum": [
"GET",
"POST",
"PUT",
"PATCH",
"DELETE"
],
"type": "string",
"description": "HTTP method (default GET)"
},
"headers": {
"type": "object",
"description": "Extra request headers (Accept/Content-Type auto-set)"
},
"max_usdc": {
"type": "number",
"description": "Spend cap for THIS call in USDC (default 0.25, must be ≤ 10)"
},
"allowed_schemes": {
"type": "array",
"items": {
"type": "string"
},
"description": "x402 schemes to accept (default ['exact'])"
},
"allowed_networks": {
"type": "array",
"items": {
"type": "string"
},
"description": "Networks to accept (default ['base'])"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "cancel_stale_offers",
"description": "Cancel marketplace offers that have been active for more than N days with no completions. Admin-only action tool.",
"inputSchema": {
"type": "object",
"properties": {
"max_age_days": {
"type": "number",
"description": "Cancel offers older than this many days (default: 14)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "check_voucher_status",
"description": "Check voucher status by code or ID. Requires a merchant agent key; only vouchers issued by the key owner's store are returned.",
"inputSchema": {
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "Voucher code (e.g. LOYAL-XXXX-XXXX-XXXX-XXXX)"
},
"voucher_id": {
"type": "string",
"description": "Voucher UUID (alternative to code)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.aspekt19/loyal-spark"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.aspekt19/loyal-spark"}) over MCP.
create_loyalty_program ~451 tokenscreate_gift_certificate ~385 tokensbazaar_pay_and_call ~300 tokensmint_loyalty_tokens ~270 tokenssend_report ~257 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.aspekt19%2Floyal-spark?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.aspekt19%2Floyal-spark?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aspekt19%2Floyal-spark.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aspekt19%2Floyal-spark.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.aspekt19%2Floyal-spark?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:48d0b17a3fd65270…, first seen 2026-10-19, included at leaf 25598 of 33,642. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable search servers · most reliable payments servers · most reliable web servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 15:25 UTC, the Aspekt19 Loyal Spark MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 4 minutes.
Aspekt19 Loyal Spark MCP server advertises 42 tools, including activate_loyalty_program, bazaar_discover_mcp_servers, bazaar_discover_resources, bazaar_pay_and_call, bazaar_probe_x402.
Point your MCP client at this streamable-http endpoint: https://api.loyalspark.online/loyalty-mcp
Glimind scanned all 42 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.