@yamo/mcp-server

Submits a YAMO block to the YAMORegistry smart contract. **IMPORTANT FORMAT REQUIREMENTS:** - blockId: Must follow YAMO naming convention: {origin}_{workflow} • Examples: "claude_chain", "aurora_weave", "document_translation" • Do NOT use sequence numbers (001, 002) - contentHash: Must be a valid bytes32 hash (32 bytes = 64 hex characters) • Format: "0x" followed by exactly 64 hexadecimal characters • Do NOT include algorithm prefixes (e.g., "sha256:") - previousBlock: Content hash of parent block. • If omitted, automatically fetches the latest block's contentHash • For genesis block: 0x0000000000000000000000000000000000000000000000000000000000000000 **Transaction Flow:** 1. If previousBlock omitted, fetches latest block from chain automatically 2. Content and files are uploaded to IPFS (if provided) 3. Block is submitted to smart contract with hash reference 4. Returns transaction hash and IPFS CID

Retrieves full block data from the YAMO blockchain. Returns: - blockId: Unique block identifier - previousBlock: Content hash of parent block - agentAddress: Ethereum address of submitter - contentHash: 32-byte hash stored on-chain - timestamp: Block submission timestamp (Unix epoch) - consensusType: Consensus mechanism used - ledger: Distributed storage reference - ipfsCID: IPFS CID if content was anchored Use for: - Verifying block existence before submission - Getting previousBlock hash for chain continuation - Auditing block metadata - Exploring chain history

Retrieves the most recently submitted YAMO block from the blockchain. Queries BlockSubmitted events to find the block with the highest timestamp, then fetches its full details including the contentHash that should be used as previousBlock for the next submission. Returns: - blockId: Unique block identifier - previousBlock: Content hash of parent block - agentAddress: Ethereum address of submitter - contentHash: 32-byte hash stored on-chain (use as previousBlock for next submission) - timestamp: Block submission timestamp (Unix epoch) - consensusType: Consensus mechanism used - ledger: Distributed storage reference - ipfsCID: IPFS CID if content was anchored Use for: - Automatically getting the chain tip for extending the chain - Fetching the contentHash to use as previousBlock in submitBlock - Discovering the latest block without knowing its ID

Performs cryptographic integrity audit of a block. **Audit Process:** 1. Fetches block metadata from blockchain 2. Downloads content from IPFS (if CID exists) 3. Re-computes SHA-256 hash of downloaded content 4. Compares computed hash vs on-chain hash 5. Returns verification result with details **For Encrypted Blocks:** - Provide encryptionKey to decrypt before verification Returns detailed audit report including: - verified: true/false integrity check result - onChainHash: Hash stored on blockchain - computedHash: Hash computed from IPFS content - ipfsCID: IPFS content identifier - agentAddress: Submitter's Ethereum address - contentPreview: First 500 chars of content

Quick hash verification against on-chain record. **IMPORTANT:** This is a SIMPLE hash comparison, NOT a full content audit. It only checks if a provided hash matches what's stored on-chain. For full integrity verification (including IPFS content), use 'yamo_audit_block'. Returns: - "VERIFIED" if hash matches on-chain record - "FAILED" if hash does not match