Qlows Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Qlows Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Bring your live qlows RFP/bid deals — and the public tender corpus — into Claude, Cursor, Windsurf, Cline, Zed, or any Model Context Protocol client.
qlows-mcp is a tiny local connector. It runs on your machine as a stdio MCP server and securely proxies tool calls to the qlows API (https://app.qlows.com). It stores nothing but your token, contains no backend logic, and is read-only — your AI can pull deal context, never write back.
Quotes. Flows. Close. qlows preps the bid; your AI drafts from real, grounded context.
# 1. Connect your account (opens the browser, you paste a token back)
npx @qlows/mcp login
# 2. Verify it works
npx @qlows/mcp test # → prints the available tools
# 3. Print the snippet for your AI client
npx @qlows/mcp configThen add qlows to your client (example: Claude Desktop, ~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"qlows": {
"command": "npx",
"args": ["-y", "@qlows/mcp"]
}
}
}Restart the client. If you didn't run login, pass the token instead:
{
"mcpServers": {
"qlows": {
"command": "npx",
"args": ["-y", "@qlows/mcp"],
"env": { "QLOWS_TOKEN": "qlw_live_…" }
}
}
}You'll need a qlows account to mint a personal token (free tier works for tender search). Sign up + mint at https://app.qlows.com/mcp.
After connecting, ask your AI:
in the most urgent one."*
next 30 days, and give me the qlows link for each."*
<deal-id> from qlows and draft the Technical Approachsection, grounding every claim in the compliance items and our approved answers."*
All tools are read-only. Personal-data tools need a personal token; the tender tools also work on a free account.
| Tool | What it does |
|---|---|
list_deals | Your RFP/bid deals (lightweight metadata) |
get_deal_snapshot | Full deal snapshot — RFP summary + compliance + Q-routing + intelligence |
search_compliance_items | Keyword search across compliance items |
get_q_routing_state | Sections + questions + answers + assignment state |
get_intelligence_summary | AI summary + tailoring detection |
list_questions | Flat question list |
list_competitors | Per-deal competitor analysis |
search_tenders | Public tender corpus search (FTS + filters) |
search_tenders_for_my_company | Personalised semantic tender search |
get_tender_detail | Full enriched record for one tender |
The connector discovers tools live from the server, so new qlows tools appear without updating this package.
| Command | Description |
|---|---|
qlows-mcp | Run the MCP server over stdio (how clients launch it) |
qlows-mcp login | Sign in via browser and store a token in ~/.qlows/config.json (0600) |
qlows-mcp test | List available tools to verify your token |
qlows-mcp config | Print config path + a client setup snippet |
qlows-mcp help | Usage |
Environment variables
QLOWS_TOKEN — API token (overrides the stored one).QLOWS_BASE_URL — defaults to https://app.qlows.com; point athttp://localhost:3000 for local testing.
MCP client (Claude/Cursor) ⇄ qlows-mcp (stdio, local) ⇄ https://app.qlows.com/api/mcp/<token>/rpcThe connector is a transparent JSON-RPC proxy. It does not implement tools — it forwards initialize, tools/list, tools/call, and resources/* to the qlows server and relays the responses. The token travels in the request to qlows over HTTPS; treat it like a password.
qlows-mcp login, or set QLOWS_TOKEN.mint a new one at https://app.qlows.com/mcp and re-run login.
validate the JSON (a stray comma silently breaks it); check the client's MCP logs.
Verify end-to-end with the MCP Inspector:
npx @modelcontextprotocol/inspector npx @qlows/mcp~/.qlows/config.json(permissions 0600). It collects no telemetry.
instantly at https://app.qlows.com/mcp.
login (loopback callback).metadata discovery on the qlows server; tracked as a backend follow-up. This connector + the MCP Registry listing are the interim distribution path.
npm install
npm run build
QLOWS_TOKEN=… QLOWS_BASE_URL=http://localhost:3000 node dist/index.js testPublishing is automated on v* tags (see .github/workflows/release.yml): npm publish → MCP Registry publish via GitHub OIDC.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.