get_dispute_resolvers
Reads registered dispute resolver entities. Use this to find a valid disputeResolverId for create_offer. Read-only. Returns: array of resolvers with ID, fees, escalationResponsePeriod, and supported tokens.
Category: Dispute management. Returns unsigned tx? No — read-only or returns signed payload.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
disputeResolversSkip | number | no | |
disputeResolversFirst | number | no | |
disputeResolversOrderBy | active | admin | assistant | clerk | escalationResponsePeriod | fees | funds | id | logs | metadataUri | offers | pendingDisputeResolver | pendingDisputeResolver__admin | pendingDisputeResolver__assistant | pendingDisputeResolver__clerk | pendingDisputeResolver__id | sellerAllowList | treasury | no | |
disputeResolversOrderDirection | asc | desc | no | |
disputeResolversFilter | object | no | |
configId | string | yes | Boson/Fermion Protocol deployment identifier. Format: '<env>-<chainId>-<index>' e.g. 'production-137-0' (Polygon mainnet), 'testing-80002-0' (Amoy testnet). Call get_config_ids to list all valid values for this server. |
Related
- Reference → MCP tools — full catalogue.
- Build for AI agents → The 3-step signing pattern — what to do with returned unsigned transactions.
- Concepts → Signing & meta-transactions — canonical signing reference.