AI Proof of Us MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIPOU_RPC_URL | No | Optional Base-compatible JSON-RPC endpoint. | |
| AIPOU_DATA_DIR | No | Optional local directory for receipt and collector state. | |
| AIPOU_CLAIMS_ADDRESS | No | AIPOU claims contract address on Base. | |
| AIPOU_CONTRACT_ADDRESS | No | AIPOU token contract address on Base. | |
| AIPOU_AGENT_PRIVATE_KEY | No | Optional private key for a dedicated farming wallet. Never use a primary wallet. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_aipou_contractA | Return the configured AIPOU token contract address, Base network details, explorer URL, and minimal ABI. |
| get_aipou_identityA | Return the dedicated farming wallet address and public Ed25519 collector key. Private keys are never returned. |
| get_aipou_statusB | Show recorded, pending, and already claimed AIPOU receipts plus the farming wallet's on-chain AIPOU balance. Does not reveal private keys or full receipt payloads. |
| estimate_ai_rewardB | Estimate the client-signed AIPOU reward before a task is completed. The final tier is derived by the validator. |
| begin_ai_task | Create a unique task nonce and EIP-712 authorization signed by the dedicated farming wallet. |
| complete_ai_taskC | Complete a unique task, derive its trust tier, reject duplicate evidence, and create an Ed25519-signed receipt. |
| export_ai_receipts | Export stored signed AI task receipts, optionally filtered by wallet. |
| settle_ai_rewards | After an explicit user claim request for one limited batch, validate eligible receipts against the settlement policy, publish a Merkle root, and mint the included rewards. Submits two on-chain transactions; the host's own confirmation policy applies. |
| settle_all_ai_rewards | After an explicit broad claim request, settle all currently pending eligible receipts from the shared AIPOU data directory by submitting as many bounded batches as needed. Each batch publishes one Merkle root and submits one claim transaction. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xddneto/AI-Proof-of-Us'
If you have feedback or need assistance with the MCP directory API, please join our Discord server