get_v1_indexers
ListIndexers reports the deployment's chain indexer(s) and how far each has indexed.
ListIndexers reports the deployment's chain indexer(s) and how far each has
indexed. Identity and health come from the indexer's /health; the latest indexed
block (height + time) from its /v1/explorer/blocks. The row EXISTS if EITHER call
reaches the indexer; when the indexer is entirely unreachable the answer degrades
to an honest-EMPTY list at 200, not a 502. No chain HEAD is exposed by the indexer
REST, so lag is honestly omitted rather than fabricated.
| Tool | get_v1_indexers |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 0 |
| Operation | GET /v1/indexers |
| Product | indexers |
Arguments
This tool declares no arguments. Call it with an empty arguments object.
Call it
A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_indexers",
"arguments": {}
}
}'tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
get_v1_indexers | GET /v1/indexers | indexers | Reports the deployment's chain indexer(s) and how far each has indexed. |
The same capability over plain HTTP is in the indexers API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?