Waqi - AI Privacy Layer
About
Waqi — hosted MCP server that redacts PII from your business tools before the AI sees them. Audit log included.
Details
- Author
- ajprolific
- Downloads
- 387
- Categories
- Database, Security, Other, AI, Search
Jump to
- Redaction before the model. PII is detected and replaced before any response leaves Waqi — the AI only ever sees cleaned data.
- Provable audit log. Every call logged: who asked, which tool, what was caught. Written after redaction, so the log itself never holds sensitive values.
- Per-person tokens. Each team member gets their own URL; every call is individually attributed, and access is revoked per person.
- Read-only by design. Waqi fetches; it never writes to your tools.
- Credentials stay encrypted. Connector keys are stored encrypted and write-only — no read-back, not even for the account owner.
- 16 business connectors across payments, accounting, CRM and communication, with more added on request.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Waqi - AI Privacy LayerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
There is nothing to install or host — Waqi runs as a managed service.
1. Sign up at bilazann.com/waqi — the dashboard gives each team member a personal MCP URL: https://waqi.bilazann.com/api/mcp/YOUR_TOKEN
2. Connect a tool (Stripe, Xero, Zoho, Slack…) in the dashboard.
3. Paste your MCP URL into your client — Claude: Settings → Connectors → Add custom connector; ChatGPT: Settings → Connectors → Developer mode.
Step-by-step guides with screenshots: bilazann.com/waqi/docs
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"waqi - ai privacy layer": {
"waqi": {
"type": "http",
"url": "https://waqi.bilazann.com/api/mcp/YOUR_TOKEN"
}
}
}
}
McpServers
{
"waqi": {
"type": "http",
"url": "https://waqi.bilazann.com/api/mcp/YOUR_TOKEN"
}
}
Waqi — the MCP server that redacts PII before the AI sees it
Waqi (واقي, "protector") is a hosted MCP server that sits between your business tools and your AI assistant.Connect Stripe, Xero, your CRM and more to Claude or ChatGPT — Waqi fetches the data read-only, strips names, card numbers and personal details, writes a provable audit entry, and only then returns the cleaned data to the model.
Your AI gets real answers from real business data. Your customers' personal data never reaches it.
- Website:bilazann.com/waqi
- Setup guides:bilazann.com/waqi/docs
This is ahosted, commercialMCP server. This repository contains its documentation and MCP Registry manifest — the service itself runs atwaqi.bilazann.com.
AI assistant ──1· tool call──▶ Waqi ──2· read-only fetch──▶ Your tools (Stripe, Xero, CRM…) ▲ │ └──3· redacted data only───┘ (audit log written AFTER redaction — the sensitive values are never stored)
- Redaction first.Names, emails, phone numbers, card numbers, addresses and other personal identifiers are detected and replaced before the response leaves Waqi.
- Provable audit log.Every call is logged — who asked, which tool, how many sensitive items were caught — so you can show clients or regulators exactly what the AI never saw.
- Per-person tokens.Each team member gets their own MCP URL; every call is individually attributed, and access is revoked per person, not per company.
- Read-only by design.Waqi fetches; it never writes to your tools.
- Credentials stay encrypted.Connector keys are stored encrypted and are never visible to anyone — including us.
You need a Waqi account (start here) — the dashboard gives each team member a personal MCP URL of the form:
https://waqi.bilazann.com/api/mcp/YOUR_TOKEN
Claude (web/desktop):Settings → Connectors →Add custom connector→ paste your MCP URL.
claude mcp add --transport http waqi https://waqi.bilazann.com/api/mcp/YOUR_TOKEN
ChatGPT:Settings → Connectors →Advanced→Developer mode→ add the same URL.
Standard MCP configuration(for clients that use a JSON config file):
{ "mcpServers": { "waqi": { "type": "http", "url": "https://waqi.bilazann.com/api/mcp/YOUR_TOKEN" } } }
Step-by-step guides with screenshots for every client and every connector:bilazann.com/waqi/docs.
Tip: in Claude, an attached connector still has to beenabled in the chatyou're using — if tools list but never run, that's the switch to check.
Stripe · Xero · Zoho Books · Zoho CRM · Slack · and more — 16 business tools across payments, accounting, CRM, and communication, with new connectors added on request (current list).
- Connector credentials: stored encrypted, write-only (no read-back UI, not even for the account owner).
- MCP tokens: only SHA-256 hashes are stored.
- Audit log: written post-redaction — the log itself never contains the sensitive values.
- Full detail:bilazann.com/waqi#trust
Self-serve, VAT-inclusive, from £99/month (annual and team plans available) —bilazann.com/waqi.
- Docs:bilazann.com/waqi/docs
- Contact: via the website
Waqi is built byBilazann. "Bilazann" means "without doubt" — Waqi is that idea applied to AI: use it fully, without doubting what it saw.
Security and compliance layer for MCP agents. The analyze_prompt tool checks any input — user messages, RAG retrievals, tool outputs — for prompt injection (22 deterministic signatures, 7 languages) and PII before your model sees it. Every verdict returns a signed audit record (SHA-256 + UUID + UTC) you can retain as GDPR Art. 30 evidence. Free tier: 10,000 requests/month.
Cited compliance, legal & security intelligence for AI agents — 300+ law, regulation and standards corpora (GDPR, NIS2, AI Act, DORA) with article-level citations, plus live CVE/KEV/EPSS vulnerability context. OAuth remote server, free tier
Require a named human's offline-verifiable approval before an AI agent takes an irreversible action — payment release, record change, deploy. Two-person rule, Ed25519 Trust Receipts, IETF-drafted, Apache-2.0.
KHEPRA MCP Server smithery badge MCP Registry License Container PQC Sovereign compliance engine with 36,195 STIG/CCI/NIST/CMMC mappings. Air-gappable. Zero token costs. Run ert_scan → get a Godfather Report with dollar-denominated business impact. The only MCP compliance server that runs on your metal — with the World's First DoD PQC STIG built in. PQC-01-STIG-V1R1 — Full Whitepaper → 17 controls covering CNSA 2.0, FIPS 203/204/205, and the NSA's May 2026 MCP security advisory. The world's first DoD-style Post-Quantum Cryptography STIG, including the first PQC controls for agentic AI and MCP deployments.
Six-gate governance for AI agents: PROCEED/PAUSE/HALT decisions with hash-chained audit trails.
Cryptographic runtime governance for AI agents. 20 tools. Sealed policy artifacts, continuous measurement, tamper-evident proof. Ed25519 + SHA-256.
AI Agent Supply Chain Security - Intercepts and validates every package installation, git clone, and script download triggered by AI coding agents before it executes.
Structured AI incident reporting for EU AI Act Article 62 — generates mandatory incident reports, severity classification, root cause analysis, and regulator-ready submissions for serious AI incidents.
Enforces organisational AI usage policies at the agent layer — blocks prohibited model calls, enforces data residency rules, logs policy violations, and ensures AI governance policies are machine-executable.
EU AI Act compliance scanner for Python AI agents — 10 tools for scanning, analysis, and remediation
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





