ArkHive MCP
PYPI · ARKHIVE-MCP
Tamper-evident memory + governance MCP for Claude Code, Cursor, Codex. Ships the Seatbelt kit.
Available components
Last scanned (15 hours ago)
Scores higher than 81% of PyPI servers
Category Memory and Knowledge
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 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 (Apache-2.0).Pass
- Actively maintained (last published 39 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1039 tokens (~86/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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.
- 21 Oct 26 0
- Provenance: unverified → fail ▼ security
- 20 Oct 26 +1
- Provenance: fail → unverified ▼ security
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 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.
- 14 Oct 26 −3
- Stability: pass → 0.80 functional
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 +2
- Security disclosure: fail → unverified ▼ functional
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 22 Oct 2026 · Analysed pypi/arkhive-mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
add_decree ~96
FOUNDER ONLY. Write a new governing decree as an immutable fossil (requires the founder key). Agents cannot add, soften, or exempt themselves from a decree — calls without the key are denied and fossiled.
| Name | Type | Req | Description |
|---|---|---|---|
| enforce | string | – | – |
| founder_key | string | yes | – |
| rules | array | – | – |
| scope | object | – | – |
| supersedes | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
birth ~74
Step 1, once: earn an identity before acting (Law 5: born, not configured). Returns a soul_id; use it or the name as `actor` from then on. Example: birth(name=Ember, covenant=[truth over comfort]).
| Name | Type | Req | Description |
|---|---|---|---|
| covenant | array | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
check_conformance ~90
Dry-run the gate: judge an artifact against every active decree whose scope matches, WITHOUT minting a token. Deterministic rules first; advisories surfaced; anything unprovable fails closed. Use before request_action to see why something would be vetoed.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | – |
| artifact | string | yes | – |
| intent | string | – | – |
| targets | array | yes | – |
No output schema declared.
No examples provided.
govern ~72
Ask may-I before acting. Deterministic, zero-LLM: any rule whose trigger appears in flags vetoes. flags/rules accept lists or {name: true} / {trigger: action} maps.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| flags | array | – | – |
| rules | array | – | – |
No output schema declared.
No examples provided.
list_decrees ~44
List the active governing decrees (id, text, scope, enforcement, rules). Read-only; anyone may call it.
| Name | Type | Req | Description |
|---|---|---|---|
| include_inactive | boolean | – | – |
No output schema declared.
No examples provided.
recall ~55
Read the latest records (newest first, optionally one actor) so you do not re-derive what you already know. Call this at the start of a session.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
remember ~77
Write one hash-linked, tamper-evident record. actor = a born soul_id or birth name. Example: remember(actor=Ember, action=shipped v0.2.1, data={pr: 42}).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| actor | string | yes | – |
| data | object | – | – |
No output schema declared.
No examples provided.
request_action ~123
The ONLY door to a consequential action (deploy, write_prod, overwrite, service_restart). Runs the decree conformance check; on pass mints a single-use, artifact-bound, 60s token the executor must present; on veto FAILS CLOSED — no token, no action. Pass the ACTUAL artifact (file contents / diff / plan) so it can be checked and hash-bound.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | – |
| actor | string | yes | – |
| artifact | string | yes | – |
| intent | string | – | – |
| targets | array | yes | – |
No output schema declared.
No examples provided.
seed_decrees ~64
FOUNDER ONLY. Seed the standing decrees (Senthar runtime, Claude build-wide, fossil-grounded, governance-is-code, embodiment-enforced, irreversible-human-signoff) if not already present. Requires the founder key.
| Name | Type | Req | Description |
|---|---|---|---|
| founder_key | string | yes | – |
No output schema declared.
No examples provided.
upgrade ~55
What ArkHive v2 (paid) adds — and, if you give your email, a free 14-day v2 trial key. Opt-in only: nothing is sent unless you provide an email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – |
No output schema declared.
No examples provided.
validate_token ~92
The executor calls this to authorize a real action. Rejects any token that is unknown, expired (>60s), already used, or bound to a different action_type / artifact / targets. On success the token is burned (single use) and the execution is fossiled.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | – |
| artifact | string | yes | – |
| targets | array | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
verify ~30
Prove the entire memory chain is unbroken (recomputes every hash). Free, local, no key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the ArkHive MCP server?
ArkHive MCP runs locally as a PyPI package, launched with uvx arkhive-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · arkhive-mcp
claude mcp add sammyboi81-arkhive -- uvx arkhive-mcp
What is the ArkHive MCP server?
ArkHive MCP is listed in the public MCP registry as io.github.sammyboi81/arkhive. Tamper-evident memory + governance MCP for Claude Code, Cursor, Codex. Ships the Seatbelt kit. This page covers its PyPI package (arkhive-mcp).
Is the ArkHive MCP server safe to use?
ArkHive MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. 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 ArkHive MCP server expose?
ArkHive MCP exposes 12 tools: birth, remember, recall, verify, upgrade, and 7 more. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.
Is the ArkHive MCP server still maintained?
ArkHive MCP is still listed as active in the MCP registry. We last reached this channel on 22 October 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 ArkHive MCP server under?
ArkHive MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.