Databroker

What databroker MCP server does

The databroker MCP server exposes the Mossforge DataBroker API to MCP clients. It provides access to UK vehicle information, aggregated MOT statistics, and deterministic utility functions through agent-callable tools. The underlying API uses pay-per-call x402 micropayments settled in USDC on Base mainnet.

The available data includes full DVSA MOT history for a UK registration, such as vehicle details, test outcomes, mileage, and recorded defects. Analytics cover reliability, mileage, vehicle parc, fuel mix, colour, and time-based UK testing patterns. Utility datasets perform deterministic checks or conversions for VINs, UK registration plates, MOT due dates, tyre sizes, and IBANs.

How it works

The MCP package runs locally through the standard input/output transport. A client starts it with npx -y @mossforge/databroker-mcp, and the process communicates with the remote API at the configured base URL.

Paid operations use a two-step confirmation flow. databroker_fetch and databroker_batch_create first return a price quote without spending funds. The request must then be called again with confirm: true. The server enforces this confirmation requirement rather than leaving payment approval to the model.

Each paid call is also checked against DATABROKER_MAX_USDC. Requests above that limit are rejected before payment. The remote API uses x402 exact-scheme payments: an unsigned request receives a 402 challenge, and a confirmed request is paid with a signed USDC authorization. A successful response includes a payment receipt.

Setup and configuration

Configure the MCP client with the package command and these environment variables:

• DATABROKER_BASE_URL: API endpoint, normally https://api.databroker.mossforge.dev.
• DATABROKER_WALLET_KEY: wallet key used to authorize payments.
• DATABROKER_MAX_USDC: maximum amount permitted for one paid call.

The README documents a self-custodied wallet-key option and Coinbase CDP signer options in the MCP server directory. Claude Desktop, Claude Code, and Cursor are shown as supported MCP clients. The service uses Base mainnet (eip155:8453) and USDC.

Tools and capabilities

The databroker MCP server names two payment-aware operations: databroker_fetch and databroker_batch_create. The first is used to request an individual dataset result and quote. The second supports batch creation and follows the same confirmation and spending controls described in the README.

Available API data is discoverable through the free /v1/discover route, which reports enabled datasets, current prices, descriptions, and provenance. Paid routes include DVSA MOT history, MOT analytics, and deterministic utility datasets. Utility responses identify their implementing standard and can be cached indefinitely because the same key always produces the same result.

Limitations and notes

Prices are configured by the service and may change, so clients should rely on the live quote or 402 challenge rather than fixed README values. MOT history is cached for 30 days, while analytics are refreshed daily from the DVSA bulk dataset. A first lookup for an unseen registration can trigger a live fetch taking roughly two to four seconds.

Malformed utility keys are rejected before payment, but a valid negative result, such as an invalid identifier, remains a paid answer. Keys containing slashes, spaces, or plus signs must be URL-encoded when using the underlying HTTP API. Payment requires a funded wallet and can settle on Base mainnet; the MCP package does not make payment automatic without explicit confirmation.