# Jito block engine: bundles and tips

The Jito block engine comprehended: send a transaction or a bundle, read bundle statuses, list tip accounts.

- Surface: `jito` (api), access: open, served now
- Origin: mainnet.block-engine.jito.wtf
- MCP endpoint: https://mcp.geckovision.tech/jito/mcp
- HTML page: https://geckovision.tech/catalog/jito

## Use cases

### Find the tip accounts before building a bundle

Ask: "Which accounts accept Jito tips?"

Tools, in order: `search_capabilities`, `getTipAccounts`

## Get started

```bash
claude mcp add --transport http jito https://mcp.geckovision.tech/jito/mcp
```

First call: `search_capabilities` with `{"query":"tip accounts for a bundle"}`.

Raw MCP over HTTP, the order for money paths, and the definition of done: https://geckovision.tech/agents.md

## Tools served now

Measured at 2026-09-02T03:01:24.414Z (server jito 1.28.1): 8 tools.

- `search_capabilities`: Find which endpoint/tool fits a natural-language intent. Returns {plan, tools}: `tools` = full schemas for just the ops that answer it; `plan` (when present) = 
- `get_capability`: Fetch ONE tool's full callable schema by name. Use this whenever you already know which tool you want (e.g. from a tools/list entry) — one schema, no ranking. C
- `query_docs`: Search the comprehended API's virtualized docs (spec-derived summaries, params, and agent-native artifacts) to understand WHY a call failed and how to rewrite i
- `sendTransaction`: Send one signed transaction with low latency (acts like a single-tx bundle)
- `sendBundle`: Send an atomic bundle of up to 5 signed transactions
- `getBundleStatuses`: Confirm a bundle landed on-chain — slot + confirmation status (max 5 ids)
- `getTipAccounts`: List the tip accounts a bundle/transaction must tip
- `getInflightBundleStatuses`: Track a submitted bundle before it lands — Invalid / Pending / Failed (max 5 ids)