Bitview

Address confirmed transactions (paginated)

get_address_confirmed_txs_after

Read-onlyIdempotent

Get the next confirmed transactions strictly older than after_txid, up to max_txs (25 by default and at most); a txid outside the address's history answers [] (Esplora-canonical pagination form, matches mempool.space).

Mempool.space docs

REST operation: GET /api/address/{address}/txs/chain/{after_txid}.

Input Schema

Name	Required	Description
`address`	Yes
`max_txs`	No	Transactions to return, at most 25 (the default); larger values return 25.
`after_txid`	Yes	Last txid from the previous page (return transactions strictly older than this)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed35 schema fields changedOct 30, 2026

removedInput schema / $defs / Addr

Removed value: -{
-  "description": "Bitcoin address string",
-  "examples": [
-    "04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f",
-    "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
-    "bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq"
-  ],
-  "type": "string"
-}

addedInput schema / $defs / Address

Added value: +{
+  "description": "Bitcoin address, or the hex public key of a P2PK output.",
+  "examples": [
+    "04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f",
+    "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
+    "bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq"
+  ],
+  "type": "string"
+}

changedInput schema / $defs / Txid / description

Previous value: -"Transaction ID (hash)"New value: +"A transaction ID: its hash."

addedInput schema / $defs / Txid / pattern
```
Added value: +"^[0-9a-f]{64}$"
```

changedInput schema / properties / address / $ref

Previous value: -"#/$defs/Addr"New value: +"#/$defs/Address"

addedInput schema / properties / max_txs

Added value: +{
+  "description": "Transactions to return, at most 25 (the default); larger values return 25.",
+  "minimum": 0,
+  "type": "integer"
+}

removedOutput schema / $defs / Addr

Removed value: -{
-  "type": "string"
-}

addedOutput schema / $defs / Address
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / $defs / BlockHash / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
removedOutput schema / $defs / Height / format
```
Removed value: -"uint32"
```

addedOutput schema / $defs / Hex

Added value: +{
+  "pattern": "^([0-9a-f]{2})*$",
+  "type": "string"
+}

removedOutput schema / $defs / RawLockTime / format
```
Removed value: -"uint32"
```
removedOutput schema / $defs / Sats / format
```
Removed value: -"uint64"
```
removedOutput schema / $defs / SigOps / format
```
Removed value: -"uint32"
```
removedOutput schema / $defs / Timestamp / format
```
Removed value: -"uint32"
```
removedOutput schema / $defs / Transaction / properties / size / format
```
Removed value: -"uint"
```
addedOutput schema / $defs / Transaction / properties / status / $ref
```
Added value: +"#/$defs/TxStatus"
```
removedOutput schema / $defs / Transaction / properties / status / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/TxStatus"
-  }
-]
```
addedOutput schema / $defs / TxIn / properties / scriptsig / allOf
```
Added value: +[
+  {
+    "$ref": "#/$defs/Hex"
+  }
+]
```
removedOutput schema / $defs / TxIn / properties / scriptsig / type
```
Removed value: -"string"
```
removedOutput schema / $defs / TxIn / properties / sequence / format
```
Removed value: -"uint32"
```
removedOutput schema / $defs / TxIn / properties / witness / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/Witness"
-  }
-]
```
addedOutput schema / $defs / TxIn / properties / witness / items
```
Added value: +{
+  "$ref": "#/$defs/Hex"
+}
```
addedOutput schema / $defs / TxIn / properties / witness / type
```
Added value: +"array"
```
removedOutput schema / $defs / TxIndex / format
```
Removed value: -"uint32"
```
addedOutput schema / $defs / TxOut / properties / scriptpubkey / allOf
```
Added value: +[
+  {
+    "$ref": "#/$defs/Hex"
+  }
+]
```
removedOutput schema / $defs / TxOut / properties / scriptpubkey / type
```
Removed value: -"string"
```

changedOutput schema / $defs / TxOut / properties / scriptpubkey_address / allOf

Previous value: -[
-  {
-    "$ref": "#/$defs/Addr"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/Address"
+  }
+]

removedOutput schema / $defs / TxVersionRaw / format
```
Removed value: -"int32"
```
addedOutput schema / $defs / TxVersionRaw / minimum
```
Added value: +0
```
addedOutput schema / $defs / Txid / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
removedOutput schema / $defs / Vout / format
```
Removed value: -"uint16"
```
removedOutput schema / $defs / Vout / maximum
```
Removed value: -65535
```
removedOutput schema / $defs / Weight / format
```
Removed value: -"uint32"
```

removedOutput schema / $defs / Witness

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful edge-case behavior: transactions strictly older than the cursor and an empty array when the txid is outside the address history.

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?

The key pagination behavior is front-loaded in the first sentence, with the documentation link and REST operation following as supporting detail. There is no wasted text.

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

Completeness5/5

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

An output schema exists, so return values need not be described in detail. Safety is covered by annotations, and the description supplies the important pagination, cursor, cap, and empty-result behavior.

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

Parameters4/5

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

Schema coverage is 67%, so baseline is 3, but the description clarifies that after_txid is exclusive and that max_txs is capped at 25 by default. It also explains that an unrecognized after_txid returns an empty array, adding meaningful cursor semantics beyond the schema.

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 and resource: get the next confirmed transactions strictly older than after_txid. The pagination framing clearly distinguishes it from the unpaginated get_address_confirmed_txs sibling, even without naming it.

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 clearly establishes pagination context through 'next' and 'after_txid' and notes the Esplora-canonical form. It lacks an explicit statement telling the agent to use get_address_confirmed_txs for the first page or naming other alternatives.

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

All Bitview 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.