Skip to main content
Glama

bitcoin-stratigraphy

by app.replit.bitcoin-stratigraphy-dashboard--charlesstrogish
OverviewDiscussionsAdmin

List Proof Attestations

proof.list
Read-onlyIdempotent

Freely discover, filter, and paginate recent zk-proof attestation lifecycle summaries. Use limit (1-100), offset (0-1000), and optional status (verified, cached, pending, invalid). Returns bounded summaries, not full proofs or receipts. Alias: proof.status. No invoice is created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPagination window size: maximum number of attestation records to return (integer, 1-100); increase offset by limit for the next page. Constraints: minimum: 1; maximum: 100. Example: 20.
offsetNoZero-based pagination skip offset (0-1000); increase by limit to page through historical attestations, but multiples of limit are not required. Constraints: minimum: 0; maximum: 1000. Example: 0.
statusNoFilter the attestation index to one lifecycle stage: verified, cached, pending, or invalid. Constraints: allowed values: verified, cached, pending, invalid. Example: "verified".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of indexed attestation records matching the optional status filter before the limit is applied. Constraints: minimum: 0. Example: 1.
attestationsYesRecent indexed proof attestations ordered from newest to oldest. Example: [{"proofHash":"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd","snapshotDigest":"1534979302823651498736582947365829473658294","status":"verified","submittedAt":"2026-09-19T06:20:00.000Z","attestationCount":1,"meshQuorum":true}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Input options for listing and discovering historical zk-SNARK proof attestations."New value: +"Filter bounded proof attestations by lifecycle status, then paginate newest-first with limit and offset; omit all fields for the first default page."
  2. Changed1 schema field changed
    • changedOutput schema / properties / attestations / items / properties / snapshotDigest / description
      Previous value: -"Canonical IPFS CID or hex digest identifier string. Example: \"1534979302823651498736582947365829473658294\"."New value: +"Decimal field digest or IPFS CID identifying the indexed telemetry snapshot. Example: \"1534979302823651498736582947365829473658294\"."
  3. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of records to return (integer, 1-100). Constraints: minimum: 1; maximum: 100. Example: 20."New value: +"Pagination window size: maximum number of attestation records to return (integer, 1-100); increase offset by limit for the next page. Constraints: minimum: 1; maximum: 100. Example: 20."
    • changedInput schema / properties / offset / description
      Previous value: -"Zero-based pagination skip offset count. Constraints: minimum: 0; maximum: 1000. Example: 0."New value: +"Zero-based pagination skip offset (0-1000); increase by limit to page through historical attestations, but multiples of limit are not required. Constraints: minimum: 0; maximum: 1000. Example: 0."
    • changedInput schema / properties / status / description
      Previous value: -"Filter records by attestation lifecycle state: verified, cached, pending, or invalid. Constraints: allowed values: verified, cached, pending, invalid. Example: \"verified\"."New value: +"Filter the attestation index to one lifecycle stage: verified, cached, pending, or invalid. Constraints: allowed values: verified, cached, pending, invalid. Example: \"verified\"."
  4. Changed21 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of records to return (integer, 1-100)."New value: +"Maximum number of records to return (integer, 1-100). Constraints: minimum: 1; maximum: 100. Example: 20."
    • changedInput schema / properties / offset / description
      Previous value: -"Zero-based pagination skip offset count."New value: +"Zero-based pagination skip offset count. Constraints: minimum: 0; maximum: 1000. Example: 0."
    • removedInput schema / properties / status / default
      Removed value: -"verified"
    • changedInput schema / properties / status / description
      Previous value: -"Filter records by attestation lifecycle state: verified, cached, pending, or invalid."New value: +"Filter records by attestation lifecycle state: verified, cached, pending, or invalid. Constraints: allowed values: verified, cached, pending, invalid. Example: \"verified\"."
    • addedInput schema / required
      Added value: +[]
    • removedOutput schema / properties / attestations / default
      Removed value: -[
-  {
-    "attestationCount": 1,
-    "meshQuorum": true,
-    "proofHash": "0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd",
-    "snapshotDigest": "1534979302823651498736582947365829473658294",
-    "status": "verified",
-    "submittedAt": "2026-09-19T06:20:00.000Z"
-  }
-]
    • changedOutput schema / properties / attestations / description
      Previous value: -"Recent indexed proof attestations ordered from newest to oldest."New value: +"Recent indexed proof attestations ordered from newest to oldest. Example: [{\"proofHash\":\"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd\",\"snapshotDigest\":\"1534979302823651498736582947365829473658294\",\"status\":\"verified\",\"submittedAt\":\"2026-09-19T06:20:00.000Z\",\"attestationCount\":1,\"meshQuorum\":true}]."
    • removedOutput schema / properties / attestations / items / properties / attestationCount / default
      Removed value: -1
    • changedOutput schema / properties / attestations / items / properties / attestationCount / description
      Previous value: -"Number of Nostr NIP-78 attestations recorded for this proof."New value: +"Number of Nostr NIP-78 attestations recorded for this proof. Constraints: minimum: 0. Example: 1."
    • removedOutput schema / properties / attestations / items / properties / meshQuorum / default
      Removed value: -true
    • changedOutput schema / properties / attestations / items / properties / meshQuorum / description
      Previous value: -"Whether this proof's attestation count meets the current mesh quorum threshold."New value: +"Whether this proof's attestation count meets the current mesh quorum threshold. Example: true."
    • removedOutput schema / properties / attestations / items / properties / proofHash / default
      Removed value: -"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd"
    • changedOutput schema / properties / attestations / items / properties / proofHash / description
      Previous value: -"0x-prefixed lowercase hexadecimal SHA-256 digest of the canonical proof."New value: +"0x-prefixed lowercase hexadecimal SHA-256 digest of the canonical proof. Example: \"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd\"."
    • removedOutput schema / properties / attestations / items / properties / snapshotDigest / default
      Removed value: -"1534979302823651498736582947365829473658294"
    • changedOutput schema / properties / attestations / items / properties / snapshotDigest / description
      Previous value: -"Canonical IPFS CID or hex digest identifier string."New value: +"Canonical IPFS CID or hex digest identifier string. Example: \"1534979302823651498736582947365829473658294\"."
    • removedOutput schema / properties / attestations / items / properties / status / default
      Removed value: -"verified"
    • changedOutput schema / properties / attestations / items / properties / status / description
      Previous value: -"Current lifecycle verification state of the indexed proof."New value: +"Current lifecycle verification state of the indexed proof. Constraints: allowed values: verified, cached, pending, invalid. Example: \"verified\"."
    • removedOutput schema / properties / attestations / items / properties / submittedAt / default
      Removed value: -"2026-09-19T06:20:00.000Z"
    • changedOutput schema / properties / attestations / items / properties / submittedAt / description
      Previous value: -"ISO 8601 UTC date string format."New value: +"ISO 8601 UTC date string format. Constraints: format: date-time. Example: \"2026-09-19T06:20:00.000Z\"."
    • removedOutput schema / properties / total / default
      Removed value: -1
    • changedOutput schema / properties / total / description
      Previous value: -"Total number of indexed attestation records matching the optional status filter before the limit is applied."New value: +"Total number of indexed attestation records matching the optional status filter before the limit is applied. Constraints: minimum: 0. Example: 1."
  5. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"Filter records by attestation lifecycle state ('verified' | 'pending' | 'failed')."New value: +"Filter records by attestation lifecycle state: verified, cached, pending, or invalid."
    • changedOutput schema / properties / attestations / items / properties / proofHash / description
      Previous value: -"64-character lowercase hexadecimal SHA-256 digest string."New value: +"0x-prefixed lowercase hexadecimal SHA-256 digest of the canonical proof."
  6. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of records to return."New value: +"Maximum number of records to return (integer, 1-100)."
    • changedInput schema / properties / offset / description
      Previous value: -"Zero-based pagination skip offset."New value: +"Zero-based pagination skip offset count."
    • changedInput schema / properties / status / description
      Previous value: -"Filter records by attestation lifecycle state."New value: +"Filter records by attestation lifecycle state ('verified' | 'pending' | 'failed')."
  7. Changed5 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of attestation records to return."New value: +"Maximum number of records to return."
    • changedInput schema / properties / offset / description
      Previous value: -"Zero-based pagination skip index."New value: +"Zero-based pagination skip offset."
    • changedOutput schema / properties / attestations / items / properties / proofHash / description
      Previous value: -"Lowercase 0x-prefixed SHA-256 fingerprint of the indexed proof."New value: +"64-character lowercase hexadecimal SHA-256 digest string."
    • changedOutput schema / properties / attestations / items / properties / snapshotDigest / description
      Previous value: -"Snapshot CID or decimal Poseidon digest bound to the indexed proof."New value: +"Canonical IPFS CID or hex digest identifier string."
    • changedOutput schema / properties / attestations / items / properties / submittedAt / description
      Previous value: -"ISO 8601 timestamp when this proof entered the lifecycle index."New value: +"ISO 8601 UTC date string format."
  8. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of attestation records to return (integer, 1 to 100). Defaults to 20."New value: +"Maximum number of attestation records to return."
    • changedInput schema / properties / offset / description
      Previous value: -"Zero-based number of matching attestation records to skip before returning the page (integer, 0 to 1000). Defaults to 0."New value: +"Zero-based pagination skip index."
    • changedInput schema / properties / status / description
      Previous value: -"Optional attestation lifecycle status filter string (e.g., 'verified', 'pending', 'rejected'). Defaults to returning records of all statuses. Example: 'verified'."New value: +"Filter records by attestation lifecycle state."
  9. Changed9 schema fields changed
    • addedInput schema / properties / status / default
      Added value: +"verified"
    • addedOutput schema / properties / attestations / default
      Added value: +[
+  {
+    "attestationCount": 1,
+    "meshQuorum": true,
+    "proofHash": "0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd",
+    "snapshotDigest": "1534979302823651498736582947365829473658294",
+    "status": "verified",
+    "submittedAt": "2026-09-19T06:20:00.000Z"
+  }
+]
    • addedOutput schema / properties / attestations / items / properties / attestationCount / default
      Added value: +1
    • addedOutput schema / properties / attestations / items / properties / meshQuorum / default
      Added value: +true
    • addedOutput schema / properties / attestations / items / properties / proofHash / default
      Added value: +"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd"
    • addedOutput schema / properties / attestations / items / properties / snapshotDigest / default
      Added value: +"1534979302823651498736582947365829473658294"
    • addedOutput schema / properties / attestations / items / properties / status / default
      Added value: +"verified"
    • addedOutput schema / properties / attestations / items / properties / submittedAt / default
      Added value: +"2026-09-19T06:20:00.000Z"
    • addedOutput schema / properties / total / default
      Added value: +1
  10. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 20,
-    "status": "verified"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "offset": 0,
+    "status": "verified"
+  }
+]
    • changedInput schema / properties / limit / default
      Previous value: -10New value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Optional integer maximum number of attestation records to return (integer, 1 to 100). Defaults to 10. Example: 20."New value: +"Maximum number of attestation records to return (integer, 1 to 100). Defaults to 20."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Zero-based number of matching attestation records to skip before returning the page (integer, 0 to 1000). Defaults to 0.",
+  "example": 0,
+  "examples": [
+    0
+  ],
+  "maximum": 1000,
+  "minimum": 0,
+  "type": "integer"
+}
  11. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety bar is low. The description adds genuine value beyond that: it discloses the return granularity (bounded summaries, not full proofs/receipts), the 'freely' no-cost framing, and that no invoice/side effect occurs. It could still note rate limits or default ordering, so not a full 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 the core action and return shape, and each clause is short. However, repeating the limit/offset ranges and status enum is redundant with the schema, and 'No invoice is created' is a somewhat cryptic trailing note that costs space without clear benefit.

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?

With an output schema present, return values need not be enumerated, and the safety profile is carried by annotations. The description covers scope, pagination, filtering, and the summary-vs-full distinction, leaving only minor gaps (ordering, rate limits) for a low-complexity read tool.

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 description coverage is 100%, so the schema already documents limit, offset, and the status enum with ranges and examples. The description restates the same ranges and enum values without adding format or behavioral nuance, which matches the baseline-3 rule.

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?

States a specific verb (list/filter/paginate) and resource (zk-proof attestation lifecycle summaries), and explicitly contrasts with the fuller siblings by noting it returns 'bounded summaries, not full proofs or receipts.' An agent can distinguish it from proof.get_by_hash and proof.verify without opening any schema.

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 clear context ('freely discover, filter, and paginate recent ... summaries') and the summary-vs-full-proof distinction implicitly routes the agent to proof.get_by_hash when a complete proof is needed. It does not spell out an explicit when-not-to-use, so it stops short of a 5.

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

All bitcoin-stratigraphy toolsInspect
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