AI Proof of Us
NPM · AIPOU-MCP-SERVER
Private signed AI task receipts with replay checks and optional validated AIPOU claims.
Available components
Last scanned (22 hours ago)
Scores higher than 87% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 4 of 15 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to 0xddneto/AI-Proof-of-Us). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 104 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 574 tokens (~63/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/aipou-mcp-server@0.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | 0xddneto/AI-Proof-of-Us |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/0xddneto/AI-Proof-of-Us/.github/workflows/npm-publish.yml@refs/heads/main |
| Rekor log index | 2218108945 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d642753a271bda5e93d647d13ff69153b8e40d93c2b971528275efe0643eec7d606667f80b1ca773a047e5f97c5477e76adabcb8e9aa2f651ce08c485 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Deprecated | 1 |
| Stale | 4 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
begin_ai_task ~56
Create a unique task nonce and EIP-712 authorization signed by the dedicated farming wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| model | string | yes | – |
| provider | string | yes | – |
| taskHash | string | yes | – |
No output schema declared.
No examples provided.
complete_ai_task ~78
Complete a unique task, derive its trust tier, reject duplicate evidence, and create an Ed25519-signed receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSeconds | integer | yes | – |
| inputTokens | integer | yes | – |
| nonce | string | yes | – |
| outputHash | – | yes | – |
| outputTokens | integer | yes | – |
| providerEvidence | object | – | – |
No output schema declared.
No examples provided.
estimate_ai_reward ~57
Estimate the client-signed AIPOU reward before a task is completed. The final tier is derived by the validator.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSeconds | integer | yes | – |
| inputTokens | integer | yes | – |
| outputTokens | integer | yes | – |
No output schema declared.
No examples provided.
export_ai_receipts ~29
Export stored signed AI task receipts, optionally filtered by wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | – | – |
No output schema declared.
No examples provided.
get_aipou_contract ~32
Return the configured AIPOU token contract address, Base network details, explorer URL, and minimal ABI.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_aipou_identity ~31
Return the dedicated farming wallet address and public Ed25519 collector key. Private keys are never returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_aipou_status ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
settle_ai_rewards ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxReceipts | integer | – | – |
No output schema declared.
No examples provided.
settle_all_ai_rewards ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | integer | – | – |
| maxBatches | integer | – | – |
No output schema declared.
No examples provided.
How do I install the AI Proof of Us MCP server?
AI Proof of Us runs locally as an npm package, launched with npx -y aipou-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · aipou-mcp-server
claude mcp add 0xddneto-ai-proof-of-us -- npx -y aipou-mcp-server
What is the AI Proof of Us MCP server?
AI Proof of Us is an MCP server listed in the public MCP registry as io.github.0xddneto/ai-proof-of-us. Private signed AI task receipts with replay checks and optional validated AIPOU claims. This page covers its npm package (aipou-mcp-server).
Is the AI Proof of Us MCP server safe to use?
AI Proof of Us scores 85 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI Proof of Us MCP server expose?
AI Proof of Us exposes 9 tools: get_aipou_contract, get_aipou_identity, get_aipou_status, estimate_ai_reward, begin_ai_task, and 4 more. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.
Is the AI Proof of Us MCP server still maintained?
AI Proof of Us is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AI Proof of Us MCP server under?
AI Proof of Us declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.