AI Proof of Us

io.github.0xddnetoPublished by GitHub account 0xddnetov0.5.0Updated Oct 24, 2026

Private signed AI task receipts with replay checks and optional validated AIPOU claims.

The publisher's own server: Proof Holdings

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Records private, signed receipts for authorized AI tasks locally and optionally claims validated AIPOU rewards on Base.

What you can do
The server creates private, signed receipts for authorized AI tasks, with replay checks, and stores them locally. It supports local receipt collection, reward status checks, and optional claims for validated work on Base. It does not detect hidden AI use, prove task quality, or require raw prompts and outputs to leave the machine.
When to use it
Use it when an agent framework needs a verifiable, framework-ready receipt ID to attach to task metadata, or when you want to check and optionally claim AIPOU rewards for validated work. Start with the demo or doctor commands to evaluate it without funds or network access.
Requirements
Node.js for the npm package aipou-mcp-server, launched over stdio. Persistent receipt collection needs one identity option: AIPOU_AGENT_KEY_FILE (recommended) or AIPOU_AGENT_PRIVATE_KEY, plus AIPOU_CLAIMS_ADDRESS and AIPOU_CONTRACT_ADDRESS. Optional AIPOU_RPC_URL and AIPOU_DATA_DIR. Default network is Base mainnet; the demo and doctor modes need no wallet, funds, or network.
Before you install
Requires a dedicated farming wallet private key, supplied via AIPOU_AGENT_PRIVATE_KEY or the recommended AIPOU_AGENT_KEY_FILE; never use a primary wallet and never commit the key. Do not set AIPOU_VALIDATOR_PRIVATE_KEY on a user installation. The local Ed25519 collector key and receipt metadata are stored unencrypted under AIPOU_DATA_DIR, so restrict that directory with OS permissions and use encrypted backups. Optional claims and settlement move funds and occur only after an explicit user- or M

Installation

In SourceWeft

  1. Open AI Proof of Us 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

AIPOU MCP Server

aipou-mcp-server records private, signed receipts for authorized AI tasks. It supports local receipt collection, reward status checks, and optional claims for validated work on Base.

It does not detect hidden AI use, prove task quality, replace payment rails, or require raw prompts and outputs to leave the user's machine.

Fast Local Adoption Test

Create and verify one disposable local receipt without cloning anything:

bash
npx -y aipou-mcp-server --demo

The command needs no wallet setup, funds, network, or claims. It prints a framework-ready workReceiptId object and deletes its ephemeral wallet, collector key, and receipt state before exiting.

To create a persistent dedicated wallet without printing its private key:

bash
npx -y aipou-mcp-server --init

The command writes a protected agent-wallet.key and prints an MCP configuration using AIPOU_AGENT_KEY_FILE. Re-running it reports the existing identity instead of overwriting the key.

Verify the persistent setup without writing files, contacting an RPC, moving funds, or submitting a claim:

bash
npx -y aipou-mcp-server --doctor

The diagnostic returns structured checks for Node.js, storage, identity, contract addresses, and chain. It prints only the public wallet address, never the private key.

From a source checkout, the same check runs with:

bash
npm installnpm run demo -w mcp-server

For a complete framework lifecycle example, continue with the adapter below.

If you are evaluating AIPOU for an agent framework, start with the lifecycle adapter example:

bash
npm installnpm run build -w mcp-servercd examples/lifecycle-adapternpm installnpm run demo

The demo launches this MCP server over stdio, creates a local signed receipt with an ephemeral wallet, and prints the receiptId reference a framework can attach to metadata. It does not claim rewards or move funds.

Run From npm

MCP clients can launch the published package with:

bash
npx -y aipou-mcp-server

Run locally from this repository

For local development or source review, run the MCP server from a checkout:

bash
npm installnpm run build -w mcp-servernode mcp-server/dist/index.js

For development:

bash
npm run dev -w mcp-server

Required configuration:

text
AIPOU_AGENT_PRIVATE_KEY=<dedicated farming wallet key>AIPOU_CONTRACT_ADDRESS=0x55f0Cc5e51A1284D20337d6cbb18938C8A1ABCbBAIPOU_CLAIMS_ADDRESS=0x4ca4C98fB784D20EdC8E2A7F531dAab4c6e53058

AIPOU_AGENT_KEY_FILE=/protected/path/agent-wallet.key is the recommended alternative to the inline private-key variable. One of the two identity options is required for persistent receipt collection.

Use a new dedicated farming wallet, never a primary wallet. Do not commit the private key. Status checks can show already claimed and pending AIPOU without moving funds. Optional claims and settlement occur only after an explicit user request.

Do not configure AIPOU_VALIDATOR_PRIVATE_KEY on a user installation. That key is only for the separate protocol validator service. The local Ed25519 collector key and receipt metadata are stored unencrypted under AIPOU_DATA_DIR; restrict that directory with operating-system permissions and use encrypted backups.

The default network is Base mainnet. AIPOU_RPC_URL and AIPOU_DATA_DIR can be set when a custom RPC endpoint or receipt directory is needed.

Publication details: docs/npm-publication.md.

Documentation

License: MIT

Source: mcp-server/README.md at commit 8ed86e1

Tools

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

Version history

1
  1. v0.5.0LatestSep 16, 2026

Score

50% 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
  • License10 pts

Other Proof integrations

Proof Holdings

holdings.proofOfficial publisher

Proof Holdings MCP server lets an assistant run identity and control verifications (phone, email, domain, wallet), manage proof tokens and delegations, and…

Streamable HTTPWeb executable
Developer Tools179 toolsNov 5, 2026

Proof of Work

Published by GitHub account kivtxs

Lets an assistant read the rules of Proof of Work, check for a local account, and create an agent account to post, vote and back claims.

STDIODesktop only
AI & ML3 toolsNov 6, 2026

QuietProof

Published by GitHub account frankjie3-create

QuietProof offers free discovery tools for a catalog of deterministic, read-only audits that are paid per call in USDC on Base via x402.

Streamable HTTPWeb executable
Finance4 toolsNov 1, 2026

SCRIPTMASTERLABS — 402Proof

com.scriptmasterlabs

Remote MCP endpoint for creating, verifying and scoring invoices settled with RLUSD on the XRPL ledger, with self-proof of settlements.

Streamable HTTPWeb executable
Business & CommerceNot indexed yetNov 5, 2026

ZKStamp Proof-100

Published by GitHub account ZKStamp

Remote MCP server that writes SHA-256 fingerprints to the BitcoinZ blockchain as shielded, dated proof-of-existence timestamps.

Streamable HTTPWeb executableAuth
Finance3 toolsOct 29, 2026