AffixIO

com.affix-ioPublished by affix-io.comOfficial publisherv1.0.0Updated Oct 26, 2026

Zero-knowledge proofs with post-quantum attestations for AI agents, without exposing personal data

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server from AffixIO that gives AI agents zero-knowledge proofs with post-quantum attestations without exposing personal data.

What you can do
  • Generates zero-knowledge proofs for AI agents
  • Issues post-quantum attestations
  • Supports proving claims without exposing personal data
  • No tool list is published, so exact operations are not documented in the supplied material
When to use it
Consider it when an agent needs to prove or attest something about a user or data set while keeping personal data private, and post-quantum attestation is a requirement.
Requirements
A remote streamable HTTP endpoint at the provider's site; OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested. The tool list and data handling are not documented here; confirm what data is sent to the provider before use.

Installation

In SourceWeft

  1. Open AffixIO in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

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/com.affix-io%2Faffixio/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "affixio": {
      "type": "http",
      "url": "https://www.affix-io.com/mcp/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 17, 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 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

    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 Affix-Io integrations