Developer · Remote MCP server
Waqi - AI Privacy Layer
Redacts PII from your business tools before the AI sees them - with a provable audit log.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ajprolific/waqi- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- ajprolific (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ajprolific) · how
- Website
- bilazann.com/waqi
- Repository
- github.com/ajprolific/waqi-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://waqi.bilazann.com/api/mcp/{token} | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Waqi - AI Privacy Layer
Waqi - AI Privacy Layer is a remote MCP server: there is nothing to install. Its endpoint is https://waqi.bilazann.com/api/mcp/{token}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {token}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| W3cW3C MCP - web-standards lookup over w3c/browser-specs (GitHub, CF-reachable). | Remote · HTTPLive check: ✓ handshake |
| WaitbusWorkstation-local event bus: agents wait on or emit CI/pytest/Docker/filesystem events, no polling. | Local · stdio |
| walkerOS FlowBuild, validate, simulate, and deploy walkerOS event pipelines. | Local · stdio |
| Wapiworld WhatsApp APICheck your WhatsApp numbers, connection status and webhooks, and send a text when you confirm. | Remote · HTTPLive check: ✓ handshake |
| WardenRegister every AI agent, log every action, prove it. EU AI Act compliance built in. | Remote · HTTPLive check: ✗ no handshake |
| WardenVerified context layer for AI coding agents - prunes, compresses, indexes, remembers. 32 MCP tools. | Local · stdio |
| WARDEN - MCP Security FirewallMCP security firewall: stdio wrap proxy or inspection tools; zero runtime dependencies. | Local · stdio |
| Warehouse MCPProduction MCP server for Postgres, Oracle, Snowflake, BigQuery, Redshift, DuckDB, MotherDuck. | Local · stdio |