Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Agent & MCP integration. CAN stamps what flows through any pipe. Verify, name, log locally.
Agent & MCP integration. CAN stamps what flows through any pipe. Verify, name, log locally.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
MCP handles tool connection and data transport. CAN handles verification, naming, and historical logging of the data retrieved via MCP. Because CAN is strictly a local operation (computing a hash, timestamping, and writing to a file), it requires zero integration with the MCP server. The server does not need to know CAN exists. Workflow: Agent requests data from an MCP tool. Agent receives the response payload. Agent locally applies a CAN stamp (WHEN, WHERE, WHAT) to the payload. Agent logs the stamp to its local index.tsv. This allows agents to verifiably recall past tool outputs without re-querying the server, proving that the data has not been mutated since it was retrieved.
The 1.9.0 release asks agent developers to evaluate CAN as a standard logging and retrieval mechanism. The following tests demonstrate standard agent operations using CAN.
Agents can natively generate the requirements for a CAN entry using standard system utilities. WHEN=$(date +%s%3N) WHERE=$(sha256sum <<< "tool_output_string" | awk '{print $1}') WHAT="tool_name.result" echo -e "$WHEN\t$WHERE\t$WHAT" >> ~/.can/index.tsv
Before trusting cached data, agents verify the integrity of the data against the hash (WHERE) stored in the CAN index. CLAIMED_HASH="a948904f2f0f479b8f8564e9d7e91d9820b5..." ACTUAL_HASH=$(sha256sum <<< "tool_output_string" | awk '{print $1}') if [ "$ACTUAL_HASH" = "$CLAIMED_HASH" ]; then # Valid (CAN) else # Invalid/Mutated (NOT) fi
A practical example of an agent logging an MCP tool execution. # 1. Execute MCP tool RESULT=$(mcp_call fetch_report "Q3_Data") # 2. Generate CAN stamp locally WHEN=$(date +%s%3N) WHERE=$(echo -n "$RESULT" | sha256sum | awk '{print $1}') WHAT="fetch_report.Q3_Data SAVE" # 3. Append to index echo -e "$WHEN\t$WHERE\t$WHAT" >> ~/.can/index.tsv
Can optionally works in parallel with location-based naming (e.g., standard file paths) while offering several technical benefits for autonomous agents: Offline Recall: Agents can verify and retrieve past MCP results without network overhead or re-querying the tool. Tamper Evidence: Hash verification guarantees that context injected into prompts is exactly what was originally returned by the tool. Search Optimization: Agents can filter local memory logs by timestamp (WHEN), exact content match (WHERE), or metadata/intent (WHAT). Decoupling: If the MCP server goes offline or the tool's API changes, the historical data remains perfectly addressable and verifiable in the agent's local state.
1.8.0: Core CAN specification (WHEN + WHERE + WHAT). 1.9.0 (Current): Agent/MCP integration and local evaluation logs. 2.x (Future): Peer-to-peer verification, physical co-presence proofs, and verifiable exchanges.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.