Inspect Artifact

Status: Live on the public MCP. Tool: inspect_artifact.

Amsterdam

Generate a BAL on Amsterdam for one plain transfer, then inspect that BAL JSON — is it well formed and does the hash match?

Look forvalidation layers and the hash check

Agent will likely call inspect_artifactWhat you can ask →

Purpose

Judge a caller-supplied structured artifact without chain state — encoding (layer A), canonical structure and item cap (layer B), optional hash match (layer C). Not consensus replay against mainnet.

Kinds (see probe inspectKinds): block-access-list (7928 BAL), authorization-list (Pectra+ set-code JSON), typed-transaction (2718 RLP), withdrawals (4895), execution-requests (7685).

MCP tool name

inspect_artifact

Inputs

Field	Required	Description
artifact	Yes	BAL JSON array or RLP hex string
kind	No	Default block-access-list
blockGasLimit	No	Decimal string for item cap check
expectedHash	No	32-byte hex blockAccessListHash

Outputs

wellFormed, structureOk, optional hashMatch / itemCapOk, errors[], computedHash, itemCount.

See Describe Capabilities for inspectKinds.

JSON schema

inspect_artifact.input.json

Inspect Artifact Changelog

Inspect Artifact Changelog

1. v0.32026-10-06Public endpoint is live.
2. v0.22026-09-22Renamed MCP tool inspect → inspect_artifact (query shape stays inspect).
3. v0.12026-09-16Implemented — structure and hash without chain state.