Bitview

Address transactions

get_address_txs

Read-onlyIdempotent

Get transaction history for an address, newest first: up to max_txs (50 by default and at most), mempool transactions first and confirmed ones filling the rest. To continue, pass the last returned txid as after_txid, or request GET /api/address/{address}/txs/chain/{after_txid} for confirmed history.

Mempool.space docs

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

Input Schema

Name	Required	Description
`address`	Yes
`max_txs`	No	Transactions to return, at most 50 (the default); larger values return 50.
`after_txid`	No	Continue after this transaction, a mempool or a confirmed one: the older ones (a confirmed cursor skips the mempool). One that is neither answers 422.

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"
+}

addedInput schema / $defs / Txid

Added value: +{
+  "description": "A transaction ID: its hash.",
+  "examples": [
+    "4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b",
+    "2bb85f4b004be6da54f766c17c1e855187327112c231ef2ff35ebad0ea67c69e",
+    "9a0b3b8305bb30cacf9e8443a90d53a76379fb3305047fdeaa4e4b0934a2a1ba"
+  ],
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}

changedInput schema / properties / address / $ref

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

addedInput schema / properties / after_txid

Added value: +{
+  "$ref": "#/$defs/Txid",
+  "description": "Continue after this transaction, a mempool or a confirmed one: the older ones (a confirmed\ncursor skips the mempool). One that is neither answers 422."
+}

addedInput schema / properties / max_txs

Added value: +{
+  "description": "Transactions to return, at most 50 (the default); larger values return 50.",
+  "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, open-world, so the burden is lower. The description still adds real behavior: result ordering, the hard 50 cap, cursor semantics that skip the mempool when a confirmed txid is supplied, and the 422 outcome for an invalid cursor.

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?

Three sentences, front-loaded with purpose, then pagination, then a docs/reference tail. Every clause carries information an agent needs; nothing is redundant padding.

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. The description still covers cap, ordering, cursor behavior, and the error case, which is everything an agent needs to invoke a 3-parameter paginated list correctly.

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% and the schema already documents the 50-item cap and cursor rules, so the description mainly restates them. It earns credit by explaining the continuation workflow ('the last returned txid as `after_txid`') and how `max_txs` interacts with mempool-first ordering, which the schema does not convey.

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?

Names a specific verb and resource ('Get transaction history for an address') and pins down scope: mixed mempool + confirmed, newest first, capped at `max_txs`. The phrase 'mempool transactions first and confirmed ones filling the rest' alone distinguishes it from siblings like get_address_confirmed_txs and get_address_mempool_txs.

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 concrete continuation instructions ('pass the last returned txid as `after_txid`') and names an alternative path for confirmed-only history. It stops short of explicitly saying when to prefer the dedicated confirmed/mempool sibling tools, so the routing guidance is clear but not exhaustive.

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.