spArxx.io | Zero-Knowledge Blockchain Timestamping

get_evidence

Returns the complete receipt kit for a single evidence item: hash, file metadata, status, and, once the on-chain job has settled, the blockchain transaction hash and explorer URL. Poll this after create_timestamp until status is 'submitted', then save the full response alongside the original file as the durable proof-of-timestamp record. This is th...

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pathParams`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The receipt kit: everything an agent needs to prove a hash was timestamped, without ever holding the original file. Save this alongside the original file, as it is the MCP equivalent of the browser's forced certificate download.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "The receipt kit: everything an agent needs to prove a hash was timestamped, without ever holding the original file. Save this alongside the original file, as it is the MCP equivalent of the browser's forced certificate download.",
+      "properties": {
+        "blockchain": {
+          "description": "Present only once status is 'submitted' and a transaction hash exists.",
+          "properties": {
+            "block_height": {
+              "description": "Decimal block number the transaction was mined in.",
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "contract_address": {
+              "description": "The TimestampRegistry contract address that storeHash(bytes32) was called on.",
+              "type": "string"
+            },
+            "explorer_url": {
+              "format": "uri",
+              "type": "string"
+            },
+            "network": {
+              "type": "string"
+            },
+            "tx_hash": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "created_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "custody_status": {
+          "description": "Custody tier (BLUEPRINT.md). MVP is self-custody only. The client is responsible for keeping this receipt with the original file.",
+          "enum": [
+            "self_custody"
+          ],
+          "type": "string"
+        },
+        "disclose_identity": {
+          "description": "Whether this specific timestamp's certificate/manifest/verify page discloses the account's name and email together, or withholds both. Frozen at creation time. Does not change retroactively if the account's default preference changes later.",
+          "type": "boolean"
+        },
+        "file": {
+          "properties": {
+            "hash": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "original_name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "size": {
+              "type": [
+                "integer",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        "id": {
+          "format": "uuid",
+          "type": "string"
+        },
+        "origin_channel": {
+          "description": "Set to 'mcp_agent' when this item was created via an MCP agent key.",
+          "enum": [
+            "mcp_agent",
+            null
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "public_verify_url": {
+          "description": "Human-viewable, Cloudflare Turnstile-protected confirmation page. Hand this to the human to open in their own browser. Do not fetch it programmatically, as it is not meant for agent traffic and will likely be blocked.",
+          "format": "uri",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "receipt_data": {
+          "description": "Structured receipt payload (shape varies: includes identity_claim block also surfaced publicly via verify_certificate).",
+          "type": "object"
+        },
+        "status": {
+          "enum": [
+            "pending",
+            "submitted",
+            "failed"
+          ],
+          "type": "string"
+        },
+        "verification_instructions": {
+          "description": "Step-by-step instructions for an agent to independently confirm the timestamp using only public blockchain data (recompute the hash locally, fetch the transaction, decode its calldata). Requires no trust in spArxx.io beyond the public chain itself. Present only once blockchain data is available.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 11, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose the key behavioral trait: the result is asynchronous and the blockchain transaction hash/explorer URL only appear 'once the on-chain job has settled,' so the caller must poll until status is 'submitted'. It does not cover auth requirements, error/not-found behavior, or rate limits on polling, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns, then the polling workflow, then what to do with the output — a logical ordering with no filler. The text is truncated mid-sentence, so it is efficient but evidently incomplete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description could have deferred return-value details, yet it helpfully summarizes the payload and, more importantly, explains the async polling lifecycle needed to interpret status. The only shortfall is that the visible text ends mid-sentence, leaving an unknown remainder of the intended guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter (pathParams.id) and the schema already describes it as the 'evidence_id returned by create_timestamp or list_evidence.' The description reinforces that this is a single-item lookup but adds no new syntax, format, or lookup detail beyond the schema. Baseline 3 for a single well-documented path parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Returns the complete receipt kit for a single evidence item' — and enumerates what the kit contains (hash, file metadata, status, tx hash, explorer URL). It clearly distinguishes itself from list_evidence and create_timestamp by scoping to a single item and naming them as the source of the id, though the truncated sentence ('This is th...') leaves the sibling differentiation against verify_certificate unfinished.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing guidance: 'Poll this after create_timestamp until status is submitted' and says what to do with the result ('save the full response alongside the original file'). That is concrete when-to-use direction, though the cut-off final sentence may have carried a when-not/alternative clause that is not visible.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All spArxx.io | Zero-Knowledge Blockchain Timestamping tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?