creem/validate-license

What it does

Validate a Creem license key and check activation status

Install Taprun once

Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:

brew install LeonTing1010/tap/taprun
tap mcp connect

Or drop this into your claude_desktop_config.json (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):

{
  "mcpServers": {
    "tap": {
      "command": "tap",
      "args": ["mcp", "start"]
    }
  }
}

Call creem/validate-license

Terminal, once installed:

tap run creem/validate-license --key creem_test_xxx --license BY5D0-xxx --instance lki_xxx

From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:

tap.run({ site: "creem", name: "validate-license", args: {"key":"creem_test_xxx","license":"BY5D0-xxx","instance":"lki_xxx"} })

Why compile it once

This plan was forged once — the AI read creem, picked stable structural addresses (JSON-LD, ARIA, RSS, or declared API endpoints, in that priority order), and saved them to a .plan.json. Every replay since then has used zero LLM tokens. When creem ships a site change that breaks the extraction, tap verify surfaces it before your data goes stale — not after your pipeline silently writes garbage for a week.

Related creem taps