Devolens / Cryptolens

@cryptolens list all license keys for product ID 12345 that expire in the next 30 days, grouped by customer

Found 47 license keys expiring between now and March 15. Breakdown by customer: Acme Corp (12 keys, all Standard tier), Beta Industries (8 keys, 3 Enterprise / 5 Standard), Gamma LLC (27 keys, mixed tiers). The earliest expiration is March 2 for key ACME-STD-8821. All keys are currently active with no blocks. This represents page 1 of 2; 23 additional keys match your filter on the next page.

Demonstrates read-heavy license inventory queries that pair product metadata with expiration logic. Requires a token with Get Key and Get Products methods enabled. The MCP returns paginated results; you must call again with next_cursor to see all matches. Customer grouping happens in the AI layer, not the API.

@cryptolens create a new license key for product 12345 assigned to customer 'Acme Corp' with Standard template, set to expire in 365 days

Created license key ACME-STD-9104 for Acme Corp under product 12345. Applied the Standard template: 5 concurrent activations allowed, feature flags A and C enabled, expires March 1 2026. The key is active immediately and visible in your Cryptolens dashboard. No activation has occurred yet; the customer must call your software's activation endpoint with this key to register their first machine.

Shows the write path for provisioning licenses programmatically. Requires a token with Create Key method enabled and knowledge of your product's template IDs (call List License Templates first if unknown). The MCP confirms creation but does not handle end-user activation—that happens when the customer's software contacts Cryptolens directly.

@cryptolens pull daily usage aggregates for the last 7 days across all products, then summarize which features are seeing the most activation attempts

Retrieved 112 daily aggregate records spanning March 1–7. Feature flag B led activation attempts with 1,847 calls (68% success rate), followed by feature A at 1,203 calls (91% success). Product 12345 accounted for 72% of all traffic; product 67890 saw a 40% week-over-week decline. Three license keys triggered rate-limit warnings on March 5. This synthesis combines raw usage data with the AI's cross-product comparison; individual aggregate records show counts and timestamps only.

Illustrates pairing the MCP's usage-data retrieval with AI reasoning to surface trends. Requires a token with the usage-aggregates method enabled. The API returns raw daily counts; the summary and percentage calculations happen in the AI layer. Useful for spotting anomalies or planning capacity, but note that aggregates lag real-time by up to 24 hours.

When Cryptolens MCP speeds up compliance reporting for small ISVs

A 6-person B2B SaaS team closes the quarter and needs to reconcile active licenses against revenue. Their finance lead opens Switchy, pulls List License Keys filtered by product, cross-references Get License Key activation metadata against their Stripe export, and flags dormant seats in under ten minutes. The MCP wins here because Cryptolens's web UI requires clicking through individual keys—List Daily Usage Aggregates surfaces the aggregate view finance actually needs. The threshold: if you're managing more than three products or need historical trend analysis beyond 90 days, you'll hit pagination limits and want a dedicated BI tool. For quarterly spot-checks on a handful of SKUs, this MCP delivers the answer faster than logging into the vendor dashboard.

Why support teams reach for this MCP during live escalations

A customer emails that their desktop app won't activate. Your two-person support team opens the ticket in Linear, switches to Switchy, runs Get License Key with the customer's key string, and sees the activation count maxed out at three devices. They immediately call List License Users to confirm which machines are registered, then update the ticket with next steps—all without waiting for an engineer or toggling between Cryptolens tabs. The MCP shines in this reactive workflow because it exposes activation metadata and user records in one conversational thread. The trade-off: if your support volume exceeds 20 license-related tickets per day, you'll want Cryptolens webhooks piped into your helpdesk instead of manual lookups. For small teams handling sporadic escalations, this MCP cuts resolution time in half.

When List Customers and templates simplify partner provisioning

A 4-person dev-tools startup signs a reseller in EMEA and needs to provision 15 trial licenses under the partner's customer group. The ops lead uses List Customers to confirm the reseller's Cryptolens customer ID, pulls List License Templates to grab the 30-day trial template, then batches the key creation in a single Switchy session. The MCP works here because Cryptolens's reseller hierarchy is opaque in the UI—List Customers surfaces the nested groups the API returns, and templates prevent manual config drift. The boundary: if you're onboarding more than two resellers per month or need approval workflows, you'll want a Zapier integration or custom script. For infrequent partner setups where you need visibility into reseller-scoped customers, this MCP is the fastest path from contract signature to live keys.