Waqi — AI Privacy Layer

io.github.ajprolificPublished by GitHub account ajprolificv1.0.1Updated Oct 25, 2026

Redacts PII from your business tools before the AI sees them — with a provable audit log.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring Business & Commerce

Server details

Identifier: io.github.ajprolific/waqi
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account ajprolific for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.ajprolific%2Fwaqi.svg)](https://sourceweft.com/mcp/io.github.ajprolific%2Fwaqi?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A hosted MCP server that sits between business tools and an AI assistant, fetching data read-only and redacting personal data before the model sees it.

What you can do: Fetch read-only data from connected business tools such as Stripe, Xero, Zoho Books, Zoho CRM and Slack, and return it to the assistant with names, emails, phone numbers, card numbers, addresses and other personal identifiers replaced by redacted values. Write an audit entry for each call recording who asked, which tool was used and how many sensitive items were caught, with the log written after redaction. Attribute every call to an individual team member through per-person MCP URLs, so access can be revoked per person. Keep connector credentials encrypted and stored write-only.
When to use it: Use it when an assistant needs answers from real payment, accounting, CRM or communication data but customer personal data must not reach the model, or when you need an auditable record of what the AI was and was not shown.
Requirements: A Waqi account and a personal MCP URL issued by the dashboard, added as a custom connector or HTTP MCP server in the client. The service is hosted at a remote endpoint and requires OAuth authentication. Connector credentials for each business tool must be supplied to Waqi. A paid subscription is required.

Before you install

This is a hosted commercial service with self-serve pricing from £99 per month. Business data and connector credentials pass through a third party, so review its security and data-handling claims before connecting accounts. The MCP URL contains a personal token and should be treated as a secret. Access is read-only by design, but the audit log records who made each call.

Installation

In SourceWeft

Open Waqi — AI Privacy Layer in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

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 a hosted, commercial MCP server. This repository contains its documentation and MCP Registry manifest — the service itself runs at waqi.bilazann.com.

How it works

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)

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.

Quickstart

You need a Waqi account (start here) — the dashboard gives each team member a personal MCP URL of the form:

Claude (web/desktop): Settings → Connectors → Add custom connector → paste your MCP URL.

Claude Code:

ChatGPT: Settings → Connectors → Advanced → Developer mode → add the same URL.

Standard MCP configuration (for clients that use a JSON config file):

json

{  "mcpServers": {    "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"    }  }}

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 be enabled in the chat you're using — if tools list but never run, that's the switch to check.

Supported connectors

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).

Security & data handling

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

Pricing

Self-serve, VAT-inclusive, from £99/month (annual and team plans available) — bilazann.com/waqi.

Support

Docs: bilazann.com/waqi/docs
Contact: via the website

Waqi is built by Bilazann. "Bilazann" means "without doubt" — Waqi is that idea applied to AI: use it fully, without doubting what it saw.

Source: README.md at commit 77b3088

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v1.0.1LatestSep 16, 2026

Score

75% 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 daysRequired25 pts
Auth declaredRequired10 pts
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
Declare a license in the repository or the registry entry.