evide_intakeLABSCO SUMMARY
It refuses to fill in declarations that belong to someone else.
hashed_by, readiness_gate, unresolved_signals and stabilization_score are never supplied on your behalf — a missing one fails the call rather than being invented, and an out-of-range score is rejected rather than clamped. The buffer works the same way: a close less than two seconds after the open is refused, because a buffer that closes instantly observed nothing. Expect boundary_readiness to default to candidate until an independent gate declares otherwise.
What it is
A bridge to the EVIDE evidentiary deposit API. It turns an agent's decisions, escalations and governance states into records that are timestamped server-side, anchored to a verified human identity, and externalised before the consequences of the decision spread.
What you get
evide_intakedeposits a finalised decision — the summary, its classification status, threshold and boundary status, and the human oversight level declared at closureevide_escalatecrystallises the agent's state before it proceeds at a contestable boundary, with triggers includingregulatory_threshold,legal_ambiguityandhuman_review_requiredevide_intake_esb,evide_buffer_observeandevide_buffer_closerun a stabilization buffer over a closure, recording how conditions settled over a real window rather than only at the crossingevide_owner_inforeturns the configured owner and agent identity without exposing the key, andevide_checkreturns verification guidance for a record already deposited- External artifacts through
evidence_referenceswith a structured hash declaration — pointer, origin and hash are anchored, and the file itself is never uploaded
Requirements
Two prerequisites, both mandatory — the server will not start without them. A DAPI number, the verified-identity layer that makes a deposit attributable to a person or organisation, obtained through a manual process requiring an identity document, a facial photo, an audio file and a short video. And an EVIDE API key on an active plan, starting at 10 intakes a month and running to 500. Install from a clone with npm install; Node.js >= 18. The client launches index.js with EVIDE_API_KEY, EVIDE_DAPI_NUMBER and EVIDE_OWNER_ID required, plus optional EVIDE_OWNER_ROLE, EVIDE_AGENT_SYSTEM and EVIDE_AGENT_ID.
Setup effort
Build from source — git clone https://github.com/emanuelcelano/evide-mcp
USE CASES
01
Recording why an agent decided what it decided
Deposit the closure with its classification, thresholds and the oversight level that applied at the time.
02
Capturing the state before a high-stakes step
Escalate at the boundary, naming the trigger and the signals that were still unresolved.
03
Showing how conditions settled after the decision
Open a buffer over the closure, record observations, and close it with a verdict and the measured window.
04
Anchoring a document without handing it over
Declare the artifact's pointer, origin and hash — the file stays where it is.
7 tools
Listed in project docs. Your client may show a different list.
evide_escalateevide_owner_infoevide_checkevide_intake_esbevide_buffer_observeevide_buffer_closeBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- Node.js >= 18
- EVIDE_API_KEY in your environment
- EVIDE_DAPI_NUMBER in your environment
- EVIDE_OWNER_ID in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/emanuelcelano/evide-mcp
cd evide-mcp
npm installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"evide": {
"command": "node",
"args": [
"<YOUR_PATH_TO_EVIDE_MCP>/index.js"
],
"env": {
"EVIDE_API_KEY": "<YOUR_EVIDE_API_KEY>",
"EVIDE_DAPI_NUMBER": "0123456789",
"EVIDE_OWNER_ID": "<YOUR_EVIDE_OWNER_ID>",
"EVIDE_OWNER_ROLE": "AI System Operator",
"EVIDE_AGENT_SYSTEM": "MyAgentSystem",
"EVIDE_AGENT_ID": "agent_xyz"
}
}
}
}
