Bitview

Address mempool transactions

get_address_mempool_txs

Read-onlyIdempotent

Get unconfirmed transactions for an address from the mempool, newest first, up to max_txs (50 by default and at most).

Mempool.space docs

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

Input Schema

Name	Required	Description	Default
`address`	Yes
`max_txs`	No	Transactions to return, at most 50 (the default); larger values return 50.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed33 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 / properties / address / $ref

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

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.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive access, and the description adds genuinely useful behavior beyond them: result ordering (newest first) and clamping semantics (values above 50 return 50). It does not mention empty-mempool behavior, but the key call-shaping traits are covered.

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?

One tight sentence front-loads the essential scope and ordering/cap behavior; the docs link and REST route are compact and directly useful for tracing the operation. No filler.

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?

An output schema exists, so return values need no explanation, and the description covers scope, ordering, and limits. Minor gaps like behavior on an empty mempool or max_txs=0 are left unaddressed but are not blocking.

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?

Both parameters are already described in the schema (address type, max_txs cap of 50), and the description largely echoes the same default/cap information. It adds no type or format detail the schema doesn't carry, so baseline 3 applies.

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 unconfirmed transactions for an address from the mempool') with a scope qualifier ('unconfirmed' / 'mempool') that separates it from confirmed-transaction siblings like get_address_confirmed_txs. An agent can pick it without inspecting schemas.

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 mempool/unconfirmed framing implies when to use it, and 'newest first' hints at the ordering contract, but there is no explicit when-to-use statement or named alternative (e.g., get_address_txs for confirmed history). Usage is inferable rather than stated.

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.