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:

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:

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:

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:

npm install
npm 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:

npm install
npm run build -w mcp-server
cd examples/lifecycle-adapter
npm install
npm 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:

npx -y aipou-mcp-server

Run locally from this repository

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

npm install
npm run build -w mcp-server
node mcp-server/dist/index.js

For development:

npm run dev -w mcp-server

Required configuration:

AIPOU_AGENT_PRIVATE_KEY=<dedicated farming wallet key>
AIPOU_CONTRACT_ADDRESS=0x55f0Cc5e51A1284D20337d6cbb18938C8A1ABCbB
AIPOU_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

• Local Receipt Mode
• Lifecycle Adapter Example
• Evidence Boundaries
• Flop and Technocore Interoperability
• Claim Validation Policy
• Tokenomics
• Security Policy

License: MIT