Bio-Safe-Audit

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Biometric data privacy auditor ensuring Zero-Knowledge compliance.

The publisher's own server: audit.domains - Domain Valuation

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that audits biometric data privacy for Zero-Knowledge compliance, with premium settlement gated behind a payment signature.

What you can do
Audit biometric data handling against Zero-Knowledge privacy compliance expectations, based on the provider's description of the service as a biometric data privacy auditor. No tool list is published, so the exact operations the assistant can call are not documented. Premium settlement is described as requiring a payment signature, suggesting some capability is paid rather than free.
When to use it
Consider it when you need an assistant to check biometric data privacy or Zero-Knowledge compliance posture and you are comfortable with a hosted third-party service. Because no tools or documentation are published, verify its actual behavior before relying on it.
Requirements
A remote SSE endpoint at the provider's hosted address; nothing to install locally. No authentication is declared, but premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature. Network access to the hosted endpoint is needed.
Before you install
The payment-signature header is a secret and an on-chain style authorization signature; treat it as sensitive and understand what it authorizes before supplying it. Premium features may involve payment. The service is hosted by a third party, so biometric or compliance data you submit leaves your machine, and with no published tools or README its behavior cannot be verified in advance.

Installation

In SourceWeft

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

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

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fbio-safe-audit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bio-safe-audit": {
      "type": "sse",
      "url": "https://bio-safe-audit-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Audit integrations