Cyan Eclipse License Server
OfficialRelated Servers
Alternatives to Cyan Eclipse License Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.MIT
- AlicenseNot gradedqualityCmaintenanceA sovereign, MIT-licensed MCP server for professional-service workflow tools that runs on your infrastructure with Ed25519 signing, enabling autonomous agents to discover and invoke tools securely.MIT
- AlicenseNot gradedqualityCmaintenanceProvides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.MIT
- AlicenseNot gradedqualityCmaintenanceA sovereign, MIT-licensed MCP server for professional-service workflow automation, enabling offline-capable, cryptographically signed operations without vendor lock-in.MIT
- AlicenseAqualityBmaintenanceCryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call. Constraints, chains, AI judgment, invoicing, and local dashboard included.244 npm1MIT
- AlicenseNot gradedqualityCmaintenanceSovereign, MIT-licensed MCP server for professional-service workflow tooling, with Ed25519 signing, offline capability, and machine-callable by AI agents.MIT
TDQS
Scored across 27 tools
The set is unusually well cross-referenced: every read tool explicitly names the sibling to use instead (license_status vs license_inspect vs license_verify vs license_list; seat_usage vs activation_list vs activation_inspect; chain_verify vs chain_verify_anchored), and the propose/execute split is clearly stated. The main residual ambiguity is license_renew vs license_supersede, which operate on the same renew-kind proposal but differ only by confirm verb and operation class — an agent could plausibly pick the wrong executor. revocation_list_get vs license_status is also a subtle boundary (published artifact vs live state), though the description warns about it.
A consistent resource_action convention dominates (license_issue, license_revoke, journal_list, receipt_get, activation_inspect, product_register, tier_define), with a coherent _propose suffix marking the two-phase pattern against bare execute verbs. Deviations: revocation_list_get appends an extra noun-plus-'get' that breaks the pattern, and principal_manage is a multi-action tool hiding create/grant/revoke behind one name. Minor but noticeable irregularities.
At 27 tools this is heavy, and the surface could be tightened (license_supersede overlaps license_renew; the journal has five read tools; propose/execute pairs double up four operation types). That said, the domain is genuinely broad — crypto-verified artefacts, two-phase issuance, append-only journal, activations, products/tiers, principals — so most tools do earn their place. It sits on the borderline of justified breadth rather than gratuitous sprawl.
Core lifecycle is fully covered: register product, define tier, propose/execute issue, renew, revoke, supersede, verify, list/inspect/status, revocation list, journal read and integrity checks, activation deactivation and stale-seat reclaim, plus principal/mandate admin. Notable gaps: there is no product or tier read tool (product_list/product_inspect, tier_list/tier_get) — after registering products and defining versioned tiers, an agent cannot enumerate or inspect them — and no activation-create path (plausibly client-driven). These are workable gaps but real ones.