For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-30T16:51:26.641587+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://api.loyalspark.online/loyalty-mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T16:51:26.641587+00:00",
"registry_status": null,
"subject": {
"id": "io.github.aspekt19/loyal-spark",
"kind": "mcp"
},
"tools": {
"names": [
"activate_loyalty_program",
"bazaar_discover_mcp_servers",
"bazaar_discover_resources",
"bazaar_pay_and_call",
"bazaar_probe_x402",
"check_voucher_status",
"confirm_mint_fee",
"create_gift_certificate",
"create_loyalty_program",
"create_personalized_offer",
"create_reward",
"delete_report",
"earn_points",
"export_customers",
"generate_program_defaults",
"get_my_profile",
"get_platform_info",
"get_program_analytics",
"get_program_workflow_status",
"get_token_balance",
"list_fee_obligations",
"list_gift_certificates",
"list_loyalty_programs",
"list_marketplace_offers",
"list_mints",
"list_my_reports",
"list_rewards",
"list_store_discount_codes",
"mark_gift_certificate_minted",
"mint_loyalty_tokens",
"redeem_reward",
"register_loyalty_program",
"revoke_gift_certificate",
"send_report",
"set_store_sales_channel",
"transfer_loyalty_tokens",
"update_program_config",
"update_program_status",
"update_report_status",
"update_reward_status",
"update_store_discount_code",
"use_voucher"
],
"names_truncated": false,
"sha256": "7cfc31c8c44a19b11e78bebe7823aaf608aeac090f3aa73c6d086bf72dcc1680"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T16:51:26.641587+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology