io.github.PiQrypt/audit-trail
NPM · @PIQRYPT/MCP-SERVER · SCANNED SEP 25
Cryptographic audit trail for AI agents. Sign, verify, export. GDPR/HIPAA/EU AI Act.
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 7 of 14 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 141 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 337 tokens (~84/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.PiQrypt/audit-trail MCP server?
io.github.PiQrypt/audit-trail runs locally as an npm package, launched with npx -y @piqrypt/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 · @piqrypt/mcp-server
claude mcp add piqrypt-audit-trail -- npx -y @piqrypt/mcp-server
{
"mcpServers": {
"piqrypt-audit-trail": {
"command": "npx",
"args": [
"-y",
"@piqrypt/mcp-server"
]
}
}
} {
"servers": {
"piqrypt-audit-trail": {
"command": "npx",
"args": [
"-y",
"@piqrypt/mcp-server"
]
}
}
} codex mcp add piqrypt-audit-trail -- npx -y @piqrypt/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"piqrypt-audit-trail": {
"type": "local",
"command": [
"npx",
"-y",
"@piqrypt/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add piqrypt-audit-trail --command npx --arg -y --arg @piqrypt/mcp-server
mcp_servers:
piqrypt-audit-trail:
command: "npx"
args: ["-y", "@piqrypt/mcp-server"] {
"McpServers": {
"piqrypt-audit-trail": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@piqrypt/mcp-server"
]
}
}
} assistant mcp add piqrypt-audit-trail -t stdio -c npx -a -y @piqrypt/mcp-server
{
"mcpServers": {
"piqrypt-audit-trail": {
"command": "npx",
"args": [
"-y",
"@piqrypt/mcp-server"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 25 Sept 2026 · Analysed npm/@piqrypt/mcp-server@1.5.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 14 packages
| Packages resolved | 14 |
|---|---|
| Stale | 7 |
| 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 →
piqrypt_export_audit ~79
Export audit trail to JSON or encrypted .pqz archive. Optionally request PiQrypt external certification for legal compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent ID to export |
| certified | boolean | – | Create certified export (requires Pro license) |
| output_format | string | – | Output format (json or encrypted pqz archive) |
No output schema declared.
No examples provided.
piqrypt_search_events ~96
Search audit trail using fast SQLite index. Filter by event type, date range, or agent ID.
| Name | Type | Req | Description |
|---|---|---|---|
| event_type | string | – | Filter by event type (e.g., "trade_executed", "decision_made") |
| from_timestamp | number | – | Start timestamp (Unix UTC seconds) |
| limit | number | – | Maximum number of results |
| to_timestamp | number | – | End timestamp (Unix UTC seconds) |
No output schema declared.
No examples provided.
piqrypt_stamp_event ~113
Sign an AI decision with PiQrypt for cryptographic audit trail. Creates AISS-1.0 signed event with Ed25519 or AISS-2.0 with Dilithium3 (post-quantum).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent identifier (e.g., "trading_bot_v1", "hr_decision_engine") |
| payload | object | yes | Event payload containing decision data (JSON object) |
| previous_hash | string | – | Optional hash of previous event for chain integrity |
No output schema declared.
No examples provided.
piqrypt_verify_chain ~49
Verify integrity of PiQrypt event chain. Validates signatures, hash chain, and detects tampering or forks.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | Array of PiQrypt events to verify |
No output schema declared.
No examples provided.
What is the io.github.PiQrypt/audit-trail MCP server?
io.github.PiQrypt/audit-trail is an MCP server listed in the public MCP registry as io.github.PiQrypt/audit-trail. Cryptographic audit trail for AI agents. Sign, verify, export. GDPR/HIPAA/EU AI Act. This page covers its npm package (@piqrypt/mcp-server).
Is the io.github.PiQrypt/audit-trail MCP server safe to use?
io.github.PiQrypt/audit-trail scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 25 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 io.github.PiQrypt/audit-trail MCP server expose?
io.github.PiQrypt/audit-trail exposes 4 tools: piqrypt_stamp_event, piqrypt_verify_chain, piqrypt_export_audit, piqrypt_search_events. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.
Is the io.github.PiQrypt/audit-trail MCP server still maintained?
io.github.PiQrypt/audit-trail is still listed as active in the MCP registry. We last reached this channel on 25 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 io.github.PiQrypt/audit-trail MCP server under?
io.github.PiQrypt/audit-trail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.