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.

Changed7 schema fields changedSep 19, 2026

addedOutput schema / properties / data / properties / blockchain / anyOf

Added value: +[
+  {
+    "properties": {
+      "block_height": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Decimal block number the transaction was mined in."
+      },
+      "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"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / data / properties / blockchain / description

Previous value: -"Present only once status is 'submitted' and a transaction hash exists."New value: +"Present only once status is 'submitted' and a transaction hash exists; null otherwise."

removedOutput schema / properties / data / properties / blockchain / properties

Removed value: -{
-  "block_height": {
-    "anyOf": [
-      {
-        "type": "integer"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "description": "Decimal block number the transaction was mined in."
-  },
-  "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"
-  }
-}

removedOutput schema / properties / data / properties / blockchain / type
```
Removed value: -"object"
```

addedOutput schema / properties / data / properties / receipt_data / anyOf

Added value: +[
+  {
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / data / properties / receipt_data / description

Previous value: -"Structured receipt payload (shape varies: includes identity_claim block also surfaced publicly via verify_certificate)."New value: +"Structured receipt payload (shape varies: includes identity_claim block also surfaced publicly via verify_certificate). Null until status is 'submitted'."

removedOutput schema / properties / data / properties / receipt_data / type
```
Removed value: -"object"
```

Changed14 schema fields changedSep 18, 2026
- addedOutput schema / properties / data / properties / blockchain / properties / block_height / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / properties / blockchain / properties / block_height / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / data / properties / file / properties / original_name / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / properties / file / properties / original_name / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / data / properties / file / properties / size / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / properties / file / properties / size / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / data / properties / origin_channel / anyOf
```
Added value: +[
+  {
+    "enum": [
+      "mcp_agent"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / properties / origin_channel / enum
```
Removed value: -[
-  "mcp_agent",
-  null
-]
```
- removedOutput schema / properties / data / properties / origin_channel / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / data / properties / public_verify_url / anyOf
```
Added value: +[
+  {
+    "format": "uri",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / properties / public_verify_url / format
```
Removed value: -"uri"
```
- removedOutput schema / properties / data / properties / public_verify_url / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / data / properties / verification_instructions / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / properties / verification_instructions / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

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.7/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and describes the asynchronous on-chain settlement, the need to poll until 'submitted', and the durable-record purpose. It stops short of documenting failure states, statuses other than 'submitted', or error behavior, and the text appears truncated.

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?

The visible text is efficient: a dense first sentence defines the return payload and a second sentence gives the workflow. The mid-word truncation at the end prevents a perfect score.

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?

For a single-parameter polling tool, the description covers the workflow, the target status, and what to do with the response, and an output schema exists for return details. It is slightly incomplete because it does not address failure/retry handling and ends mid-sentence.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needed to compensate for the required id parameter, but it never mentions the parameter or how to populate it. The schema's own id description is helpful, but the tool description adds no parameter-level meaning.

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?

The description opens with a precise verb and resource: returns the complete receipt kit for a single evidence item, listing hash, file metadata, status, and on-chain transaction details. It is clearly distinguished from list_evidence by the 'single evidence item' framing, though it does not explicitly name the sibling alternative.

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?

The description gives an explicit workflow: poll after create_timestamp until status is 'submitted', then save the response as the proof-of-timestamp record. This is strong when-to-use guidance, but it does not state when not to use the tool or name alternatives such as list_evidence for multi-item retrieval.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?