Transaction Monitoring

Address transaction history with filtering, decoding hints, and pagination.

data , 2 MCP tools

Related workflow

Full steps, failures, and recovery live on the workflow page. This page lists tools and API references.

Incoming Payment Monitor

Why agents use it

Lets agents reconstruct what happened to an address without scanning blocks.

MCP tools

get_transaction_history
get_block_by_time

Example: get_transaction_history

A representative invocation. Drop this into an MCP-capable agent (Claude Desktop, Claude Code, Cursor, Windsurf) after the Tatum MCP server is configured.

get_transaction_history

mcp.tatumio.get_transaction_history({
  chain:   "ethereum-mainnet",
  address: "0xab5801a7d398351b8be11c439e05c5b3259aec9b",
  pageSize: 25
})
// → { transactions: [{ hash, from, to, value, ... }], cursor: "..." }

OpenAPI references

https://docs.tatum.io/openapi/blockchain-data-1.json (Transactions API)

Notes

Canonical recipe

For ongoing monitoring prefer Incoming Payment Monitor (webhooks). For historical reconstruction use get_transaction_history via MCP or the Transactions API.

Risk

Read-only. Be conservative with very wide time ranges on busy chains.