Lupin

ai.qompassPublished by qompass.aiv1.0.0Updated Nov 3, 2026

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

VerifiedSTDIODesktop onlyFinance

Overview

Lupin's local MCP server, published by qompass.ai; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
qompass.ai

Installation

In SourceWeft

  1. Open Lupin in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

json
{  "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.

Source: README.md at commit fa910e0

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

2
  1. v1.0.0LatestNov 3, 2026
  2. v0.1.0Oct 21, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts