ActionProof
NPM · ACTIONPROOF · SCANNED SEP 21
Tamper-proof audit trail for AI agents. Signed receipts, offline-verifiable, zero backend.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 82 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 372 tokens (~124/item across 3 items; 3 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the ActionProof MCP server?
ActionProof runs locally as an npm package, launched with npx -y actionproof. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · actionproof
claude mcp add burakfenerci5-actionproof -- npx -y actionproof
{
"mcpServers": {
"burakfenerci5-actionproof": {
"command": "npx",
"args": [
"-y",
"actionproof"
]
}
}
} {
"servers": {
"burakfenerci5-actionproof": {
"command": "npx",
"args": [
"-y",
"actionproof"
]
}
}
} codex mcp add burakfenerci5-actionproof -- npx -y actionproof
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"burakfenerci5-actionproof": {
"type": "local",
"command": [
"npx",
"-y",
"actionproof"
],
"enabled": true
}
}
} openclaw mcp add burakfenerci5-actionproof --command npx --arg -y --arg actionproof
mcp_servers:
burakfenerci5-actionproof:
command: "npx"
args: ["-y", "actionproof"] {
"McpServers": {
"burakfenerci5-actionproof": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"actionproof"
]
}
}
} assistant mcp add burakfenerci5-actionproof -t stdio -c npx -a -y actionproof
{
"mcpServers": {
"burakfenerci5-actionproof": {
"command": "npx",
"args": [
"-y",
"actionproof"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 21 Sept 2026 · Analysed npm/actionproof@0.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
attest_action Attest an action ~238
Create a signed, tamper-evident receipt that THIS agent performed an action (e.g. sent an email, filed a form, made a payment). Call it right after you perform the action. Returns a SignedReceipt you can store or share; anyone can later verify it offline.
| Name | Type | Req | Description |
|---|---|---|---|
| delegation_by | string | – | did:key or id of the principal who authorized this action, if any. |
| delegation_ref | string | – | Pointer to the grant (OAuth grant, AP2 mandate URL/URN). |
| delegation_scope | string | – | Authority granted, e.g. 'email.send'. |
| outcome | string | – | Outcome of the action. Defaults to 'ok'. |
| params | – | – | The action's inputs. Stored only as a hash (privacy-preserving). |
| result | – | – | The observed result/response. Stored only as a hash. |
| summary | string | – | Human-readable one-line description of what was done. |
| target | string | – | System/resource acted upon, e.g. 'acme-crm'. |
| type | string | yes | Action verb in reverse-dot form, e.g. 'email.send', 'payment.send'. |
No output schema declared.
No examples provided.
get_identity Get this agent's identity ~33
Return this ActionProof server's stable agent identity (a did:key). Receipts from attest_action are signed by this identity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_receipt Verify a receipt ~101
Verify a signed ActionProof receipt offline. Returns whether the signature is valid and which agent did:key signed it. Optionally re-check that supplied params/result match the hashes in the receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| expect_params | – | – | If provided, verify these params match the receipt's params_hash. |
| expect_result | – | – | If provided, verify this result matches the receipt's result_hash. |
| signed_receipt | string | yes | The SignedReceipt JSON (as produced by attest_action). |
No output schema declared.
No examples provided.
What is the ActionProof MCP server?
ActionProof is an MCP server listed in the public MCP registry as io.github.Burakfenerci5/actionproof. Tamper-proof audit trail for AI agents. Signed receipts, offline-verifiable, zero backend. This page covers its npm package (actionproof).
Is the ActionProof MCP server safe to use?
ActionProof scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 ActionProof MCP server expose?
ActionProof exposes 3 tools: attest_action, verify_receipt, get_identity. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.
Is the ActionProof MCP server still maintained?
ActionProof is still listed as active in the MCP registry. We last reached this channel on 21 September 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 ActionProof MCP server under?
ActionProof declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.