Ext Ops Panel
Open dashboard
Comparison

smile-webhooks vs Lumière PayCheck

smile-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Lumière PayCheck is an MCP server published by Book0fEli. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacesmile-webhooksLumière PayCheck
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 92
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.8.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

smile-webhooks vs Lumière PayCheck
Factsmile-webhooksLumière PayCheck
Marketplaces that list it11
Stars (GitHub) (differs)92 (better)0 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last release (differs)Not published2026-10-18
Where it runs (differs)Installs as a plugin bundleRemote server (lumierepaycheck.org/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/book0feli/lumiere-paycheck
Changes in the last 7 days (differs)23
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

smile-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Smile API (getsmileapi.com) webhooks. Use when setting up a Smile webhook endpoint, verifying the Smile-Signature header (HMAC-SHA512 hex over the raw body), debugging Smile signature verification failures, or handling employment/income data events like ACCOUNT_CONNECTED, TASK_FINISHED, INCOMES_ADDED, EMPLOYMENTS_ADDED, IDENTITY_ADDED, and RECORD_COMPLETED. This is Smile API for Southeast Asian employment/income data — NOT Smile.io loyalty and NOT Smile Identity KYC.

Lumière PayCheck

In its own words, on Official MCP Registry:

Check any x402 endpoint before your AI agent pays it: trust grade, verdict, and hijack checks.

How to run each

smile-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install smile-webhooks@webhook-skills

Lumière PayCheck

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Lumière PayCheck has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of smile-webhooks nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of smile-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: smile-webhooks · What it can do: Lumière PayCheck · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built