AuthProof

io.github.kaleckhPublished by GitHub account kaleckhv0.3.0Updated Oct 24, 2026

Signed, non-replayable API auth. Agents self-register and sign requests with ERC-8128.

The publisher's own server: Proof Holdings

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant self-register and sign API requests with an agent wallet key for non-replayable authentication.

What you can do
AuthProof is a local MCP server that provides signed, non-replayable API authentication. According to its registry description, agents self-register and sign requests using ERC-8128. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to authenticate to an API with per-request signatures rather than a shared static token, and when replay protection matters. It is a desktop-only local process, so it is not suitable for hosted or browser-based use.
Requirements
Runs locally over stdio, installed from the npm package @authproof/mcp-server, so Node.js is needed. It requires environment variables: AGENT_PRIVATE_KEY, AUTHPROOF_CHAIN_ID, AUTHPROOF_RPC_URL and AUTHPROOF_SERVER. Network access to the configured RPC and server endpoints is implied.
Before you install
AGENT_PRIVATE_KEY is a wallet private key supplied in hex; anyone who obtains it controls that wallet, so store it carefully and use a dedicated low-value key. AUTHPROOF_RPC_URL is described as being for auto-payment, which suggests transactions may be sent and funds spent. Signing requests sends authentication data to the configured AuthProof server.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Proof integrations