English Français العربية

Lupin

Official registry Other

Revenue-alignment MCP server: opportunity ledger, capability matching, Qompass/NTRanch lanes.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

MCPB package https://github.com/qompassai/lupin/releases/download/v0.1.0/lupin-mcp-0.1.0-linux-x64.mcpb

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Lupin
  2. How it runs
  3. Tools
  4. Client config
  5. Registry
  6. License

Lupin

An MCP server for the Revenue Alignment Engine: an opportunity ledger and capability registry with lane-scoped access. Opportunities live in one of two lanes — Qompass (sfw) or NTRanch (nsfw) — and a caller scoped to one lane can never see the other lane's entries.

Lupin is a single Rust binary. It speaks MCP over stdio (NDJSON JSON-RPC) to the client and works on plain files under a data root — no database, no network listener. It is the ledger side of the estate's revenue pipeline; the research-feed server phaedrus drafts candidates into it.

How it runs

  • Data root (ledger, capability registry, scan inbox): --root <path> or the REVENUE_ROOT environment variable (default ~/workspace/revenue-alignment-20261019).
  • Lane scope: --lane-scope operator|sfw (default operator). The operator scope sees both lanes; an sfw-scoped caller can never see nsfw entries.
  • Read-mostly by design: the only write files a candidate into the scan inbox (opportunity_submit). The validated ledger is never written by this server, and capability_match is advisory only — it never auto-aligns an opportunity.

Tools

ToolWhat it returns
capability_listThe capability registry (the alignment vocabulary); lane scope enforced
capability_matchAdvisory keyword match of free text against capabilities; never auto-aligns
opportunity_getOne ledger entry by id, including its raw block
opportunity_listLedger opportunities, optionally filtered by status; lane scope enforced
opportunity_submitFile a candidate into the scan inbox; never writes the ledger
pipeline_summaryCounts by status/lane plus parse health — the value-demonstration view

Client config

{
  "mcpServers": {
    "lupin": {
      "command": "/path/to/lupin",
      "args": []
    }
  }
}

Registry

server.json in this repo is the MCP Registry record for ai.qompass/lupin. The server is distributed as an MCPB bundle attached to the GitHub releases (Linux x64).

License

Apache-2.0 — see LICENSE.

Frequently asked questions

What is Lupin?

Revenue-alignment MCP server: opportunity ledger, capability matching, Qompass/NTRanch lanes.

How do I install Lupin?

Follow the installation steps in its documentation, shown on this page and in its repository.

Does Lupin need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Lupin open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Lupin?

It is published by qompassai. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.