satoshidata — Bitcoin entity intelligence

verify_timestamp

Verify a detached OpenTimestamps proof against the Bitcoin blockchain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "proof_base64": "<proof_base64>"
    },
    "name": "verify_timestamp"
  }
}

Input Schema

Name	Required	Description	Default
`proof_base64`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`endpoint`	Yes
`status_code`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 26, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must communicate behavioral traits. It only states that it 'verifies', without disclosing side effects (e.g., read-only), error handling, or prerequisites. This is a significant gap for a verification tool.

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

Conciseness5/5

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

A single, clear sentence with no redundant words. The description is efficient and front-loaded.

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

Completeness3/5

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

For a simple one-parameter tool with an output schema, the description covers the core purpose but lacks usage guidance and behavioral details. It is minimally adequate but leaves out important context like what happens when a proof is invalid.

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?

Schema coverage is 0%, so the description must compensate. It mentions 'detached OpenTimestamps proof', which gives context to the proof_base64 parameter, but it does not elaborate on format requirements or constraints beyond what the param name implies. Partial compensation only.

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

Purpose5/5

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

The description clearly states the tool's specific action: verifying a detached OpenTimestamps proof against the Bitcoin blockchain. This distinguishes it from sibling tools like timestamp_hash and timestamp_quote, which involve different steps in the timestamping process.

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

Usage Guidelines3/5

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

The description implies usage when you have a detached OpenTimestamps proof to verify, but it does not explicitly mention when to use this tool versus alternatives like timestamp_hash or tx_verify. It lacks explicit exclusions or alternative tool references.

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

All satoshidata — Bitcoin entity intelligence 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?