Ofrece acceso mediante pago por consulta al historial de MOT de vehículos en el Reino Unido y analíticas de fiabilidad utilizando micropagos automáticos en USDC sobre Base.
También conocido como mossforge/databroker, @mossforge/databroker-mcp
- Stars
- 0
- Herramientas
- 6
- Descargas, 30 días
- —
- Última versión
- 0.5.0
- Último commit
- 30 ago 2026
- Licencia
- MIT
¿Qué es databroker MCP?
Ofrece acceso mediante pago por consulta al historial de MOT de vehículos en el Reino Unido y analíticas de fiabilidad utilizando micropagos automáticos en USDC sobre Base. Expone 6 herramientas, como databroker_discover, databroker_fetch, databroker_meta.
Resumen generado a partir del README del proyecto
Acerca del MCP server de databroker
Con este servidor es posible acceder al historial de MOT de vehículos del Reino Unido y a analíticas de fiabilidad a través de un agente de IA. Proporciona inteligencia con modelo de pago por consulta para desarrolladores que utilizan clientes como Claude Desktop, Claude Code o Cursor. En lugar de las suscripciones tradicionales o las API keys, el sistema utiliza micropagos automáticos en USDC en la mainnet de Base para pagar por puntos de datos específicos.
Los usuarios interactúan con el servidor mediante herramientas como databroker_discover para ver los conjuntos de datos disponibles, databroker_fetch para puntos de datos individuales y databroker_batch_create para recuperar hasta 100 claves en un solo trabajo. Para evitar costes inesperados, el servidor requiere una cotización antes de realizar cualquier pago y aplica un límite por consulta definido por la variable de entorno DATABROKER_MAX_USDC.
La configuración implica conectar una wallet EOA con fondos mediante una clave privada o utilizar una wallet gestionada por Coinbase CDP. Para mayor seguridad, el servidor puede utilizar la elicitación de MCP para solicitar la aprobación manual de un humano para cada cargo en los clientes compatibles. Esto garantiza que el modelo de IA no pueda gastar fondos sin el consentimiento directo del usuario.
Qué puedes hacer con él
- 1Verificar el historial de MOT de un vehículoPide a un agente de IA que compruebe los registros de MOT y la autenticidad del kilometraje de una matrícula específica.
- 2Explorar conjuntos de datos disponiblesLista todos los conjuntos de datos habilitados y sus precios específicos en USDC antes de solicitar los datos.
- 3Realizar recuperación de datos por lotesSolicita hasta 100 claves de vehículos diferentes de un conjunto de datos utilizando un único trabajo por lotes y un solo pago.
- 4Comprobar la actualidad de los datosInspecciona la fuente y la vigencia de un punto de datos sin incurrir en ningún coste.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar databroker MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar databroker MCP en Claude Code
$ claude mcp add --env 'DATABROKER_BASE_URL=<DATABROKER_BASE_URL>' --env 'CDP_API_KEY_ID=<YOUR_CDP_API_KEY_ID>' --env 'CDP_API_KEY_SECRET=<YOUR_CDP_API_KEY_SECRET>' --env 'CDP_WALLET_SECRET=<YOUR_CDP_WALLET_SECRET>' --env 'DATABROKER_WALLET_KEY=<YOUR_DATABROKER_WALLET_KEY>' databroker -- npx -y @mossforge/databroker-mcpInstalar databroker MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"databroker": {
"command": "npx",
"args": [
"-y",
"@mossforge/databroker-mcp"
],
"env": {
"DATABROKER_BASE_URL": "<DATABROKER_BASE_URL>",
"CDP_API_KEY_ID": "<YOUR_CDP_API_KEY_ID>",
"CDP_API_KEY_SECRET": "<YOUR_CDP_API_KEY_SECRET>",
"CDP_WALLET_SECRET": "<YOUR_CDP_WALLET_SECRET>",
"DATABROKER_WALLET_KEY": "<YOUR_DATABROKER_WALLET_KEY>"
}
}
}
}Instalar databroker MCP en VS Code
.vscode/mcp.json
{
"servers": {
"databroker": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mossforge/databroker-mcp"
],
"env": {
"DATABROKER_BASE_URL": "<DATABROKER_BASE_URL>",
"CDP_API_KEY_ID": "<YOUR_CDP_API_KEY_ID>",
"CDP_API_KEY_SECRET": "<YOUR_CDP_API_KEY_SECRET>",
"CDP_WALLET_SECRET": "<YOUR_CDP_WALLET_SECRET>",
"DATABROKER_WALLET_KEY": "<YOUR_DATABROKER_WALLET_KEY>"
}
}
}
}Instalar databroker MCP en VS Code CLI
$ code --add-mcp '{"name":"databroker","type":"stdio","command":"npx","args":["-y","@mossforge/databroker-mcp"],"env":{"DATABROKER_BASE_URL":"<DATABROKER_BASE_URL>","CDP_API_KEY_ID":"<YOUR_CDP_API_KEY_ID>","CDP_API_KEY_SECRET":"<YOUR_CDP_API_KEY_SECRET>","CDP_WALLET_SECRET":"<YOUR_CDP_WALLET_SECRET>","DATABROKER_WALLET_KEY":"<YOUR_DATABROKER_WALLET_KEY>"}}'Instalar databroker MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"databroker": {
"command": "npx",
"args": [
"-y",
"@mossforge/databroker-mcp"
],
"env": {
"DATABROKER_BASE_URL": "<DATABROKER_BASE_URL>",
"CDP_API_KEY_ID": "<YOUR_CDP_API_KEY_ID>",
"CDP_API_KEY_SECRET": "<YOUR_CDP_API_KEY_SECRET>",
"CDP_WALLET_SECRET": "<YOUR_CDP_WALLET_SECRET>",
"DATABROKER_WALLET_KEY": "<YOUR_DATABROKER_WALLET_KEY>"
}
}
}
}Instalar databroker MCP en Codex
$ codex mcp add databroker --env 'DATABROKER_BASE_URL=<DATABROKER_BASE_URL>' --env 'CDP_API_KEY_ID=<YOUR_CDP_API_KEY_ID>' --env 'CDP_API_KEY_SECRET=<YOUR_CDP_API_KEY_SECRET>' --env 'CDP_WALLET_SECRET=<YOUR_CDP_WALLET_SECRET>' --env 'DATABROKER_WALLET_KEY=<YOUR_DATABROKER_WALLET_KEY>' -- npx -y @mossforge/databroker-mcpInstalar databroker MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.databroker] command = "npx" args = ["-y", "@mossforge/databroker-mcp"] [mcp_servers.databroker.env] DATABROKER_BASE_URL = "<DATABROKER_BASE_URL>" CDP_API_KEY_ID = "<YOUR_CDP_API_KEY_ID>" CDP_API_KEY_SECRET = "<YOUR_CDP_API_KEY_SECRET>" CDP_WALLET_SECRET = "<YOUR_CDP_WALLET_SECRET>" DATABROKER_WALLET_KEY = "<YOUR_DATABROKER_WALLET_KEY>"
Instalar databroker MCP en Gemini CLI
$ gemini mcp add -s user -e 'DATABROKER_BASE_URL=<DATABROKER_BASE_URL>' -e 'CDP_API_KEY_ID=<YOUR_CDP_API_KEY_ID>' -e 'CDP_API_KEY_SECRET=<YOUR_CDP_API_KEY_SECRET>' -e 'CDP_WALLET_SECRET=<YOUR_CDP_WALLET_SECRET>' -e 'DATABROKER_WALLET_KEY=<YOUR_DATABROKER_WALLET_KEY>' databroker npx -- -y @mossforge/databroker-mcpInstalar databroker MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"databroker": {
"command": "npx",
"args": [
"-y",
"@mossforge/databroker-mcp"
],
"env": {
"DATABROKER_BASE_URL": "<DATABROKER_BASE_URL>",
"CDP_API_KEY_ID": "<YOUR_CDP_API_KEY_ID>",
"CDP_API_KEY_SECRET": "<YOUR_CDP_API_KEY_SECRET>",
"CDP_WALLET_SECRET": "<YOUR_CDP_WALLET_SECRET>",
"DATABROKER_WALLET_KEY": "<YOUR_DATABROKER_WALLET_KEY>"
}
}
}
}Herramientas de databroker MCP 6
Detectado desde el READMEdatabroker_discoverdatabroker_fetchdatabroker_metadatabroker_healthdatabroker_batch_createdatabroker_batch_status
| databroker_discover | — | |
| databroker_fetch | — | |
| databroker_meta | — | |
| databroker_health | — | |
| databroker_batch_create | — | |
| databroker_batch_status | — |
Configuración
DATABROKER_BASE_URLObligatorioBase URL of the DataBroker API, e.g. https://api.databroker.mossforge.dev
CDP_API_KEY_IDSecretoCoinbase CDP API key id. Required when DATABROKER_SIGNER=cdp.
CDP_API_KEY_SECRETSecretoCoinbase CDP API key secret. Required when DATABROKER_SIGNER=cdp.
CDP_WALLET_SECRETSecretoCoinbase CDP wallet secret. Required when DATABROKER_SIGNER=cdp.
DATABROKER_WALLET_KEYSecreto0x-prefixed private key for the paying wallet. Required when DATABROKER_SIGNER=raw (the default).
DATABROKER_MAX_USDCPer-call spend cap in USDC. Calls priced above this are declined before payment.
DATABROKER_SIGNERSigner provider: "raw" (default, self-custodied private key) or "cdp" (Coinbase CDP-managed wallet)
| Nombre | Descripción | Tipo |
|---|---|---|
| DATABROKER_BASE_URL | Base URL of the DataBroker API, e.g. https://api.databroker.mossforge.dev | Obligatorio |
| CDP_API_KEY_ID | Coinbase CDP API key id. Required when DATABROKER_SIGNER=cdp. | Secreto |
| CDP_API_KEY_SECRET | Coinbase CDP API key secret. Required when DATABROKER_SIGNER=cdp. | Secreto |
| CDP_WALLET_SECRET | Coinbase CDP wallet secret. Required when DATABROKER_SIGNER=cdp. | Secreto |
| DATABROKER_WALLET_KEY | 0x-prefixed private key for the paying wallet. Required when DATABROKER_SIGNER=raw (the default). | Secreto |
| DATABROKER_MAX_USDC | Per-call spend cap in USDC. Calls priced above this are declined before payment. | |
| DATABROKER_SIGNER | Signer provider: "raw" (default, self-custodied private key) or "cdp" (Coinbase CDP-managed wallet) |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblemossforge/databroker is public and reachablegithub.com/mossforge/databroker ↗Aprobado
- El paquete indica este repositorio como su origen@mossforge/databroker-mcp names mossforge/databroker as sourcenpmjs.com/package/@mossforge/databroker-mcp ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for @mossforge/databroker-mcpnpmjs.com/package/@mossforge/databroker-mcp/v/0.5.0#provenan ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-08-30github.com/mossforge/databroker ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @mossforge/databroker-mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependencias198 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo6 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubdatabroker-mcp-server
Give any MCP-capable agent (Claude Desktop, Claude Code, Cursor, etc) pay-per-call access to MossForge DataBroker — UK vehicle MOT intelligence, UK-wide reliability analytics — with x402 USDC micropayments on Base mainnet handled automatically. No API keys, no subscription: fund a wallet, ask questions.
Tools
| Tool | Cost | Purpose |
|---|---|---|
databroker_discover |
free | List enabled datasets, their kind, and per-call USDC prices |
databroker_fetch |
free to quote, paid to confirm | Fetch a single datapoint for a dataset + key |
databroker_meta |
free | Staleness/TTL/source info for a datapoint, without paying for it |
databroker_health |
free | API uptime check |
databroker_batch_create |
free to quote, paid to confirm | Fetch up to 100 keys from one on-demand dataset in a single job, one payment total |
databroker_batch_status |
free | Poll a batch job created by databroker_batch_create |
Payments are never automatic. databroker_fetch and databroker_batch_create always quote the price first — nothing is paid until the tool is called again with confirm: true. Every paid call is also capped by DATABROKER_MAX_USDC (default 0.50); a call priced above the cap is declined before anything is paid.
Payment approval is enforced by the server, not by the calling model, on clients that support it. Immediately before any payment, this server sends an MCP elicitation request through the connected client, asking the human directly to approve or decline the exact charge — independent of whatever confirm value the model passed. Claude Code (CLI) supports this as of v2.1.76; other clients (Claude Desktop, Cursor, etc.) may not yet.
If the connected client doesn't advertise elicitation support, the server falls back to the pre-elicitation guarantee — confirm: true from the calling model, still capped by DATABROKER_MAX_USDC — rather than blocking every paid call. Set DATABROKER_REQUIRE_ELICITATION=true to instead hard-block paid calls on clients without elicitation support, if you know your client supports it and want the stricter guarantee. The server logs which mode is active on startup and the first time a non-elicitation client connects.
Setup
-
Create a fresh EOA wallet and fund it with a few USDC on Base mainnet (plus nothing else — no ETH needed; EIP-3009 transfers are gasless for the payer).
-
Add to Claude Desktop (
claude_desktop_config.json):
{
"mcpServers": {
"databroker": {
"command": "npx",
"args": ["-y", "@mossforge/databroker-mcp"],
"env": {
"DATABROKER_BASE_URL": "https://api.databroker.mossforge.dev",
"DATABROKER_WALLET_KEY": "0x...",
"DATABROKER_MAX_USDC": "0.50"
}
}
}
}
claude mcp add --transport stdio \
--env DATABROKER_BASE_URL=https://api.databroker.mossforge.dev \
--env DATABROKER_WALLET_KEY=0x... \
databroker -- npx -y @mossforge/databroker-mcp
- Ask: "Should I buy this 2018 Golf, reg AB18 CDE? Check its MOT history and whether the mileage looks genuine."
Who holds the wallet
Two signer providers are supported, set via DATABROKER_SIGNER:
raw(default) — a private key you hold, read fromDATABROKER_WALLET_KEY. Zero setup beyond a funded wallet, but the key material is only as safe as this process's environment, and the spend cap is enforced by this codebase alone.cdp— pays from a Coinbase CDP-managed wallet. No private key ever touches this process; CDP signs remotely and can enforce spend policies (session caps, allowed tokens) at the custodian layer. Requires a CDP account andCDP_API_KEY_ID/CDP_API_KEY_SECRET/CDP_WALLET_SECRET, plusnpm install @coinbase/cdp-sdk(it's an optional dependency, not installed by default).
Security notes
- Use a dedicated, low-balance wallet. In
rawmode the key never leaves your machine; payments are signed locally via the@x402/*v2 protocol stack (@x402/fetch+@x402/core/client+@x402/evm/exact/client), producing EIP-3009transferWithAuthorizationpayloads. - The per-call cap (
DATABROKER_MAX_USDC) is the blast radius for any single call and is checked before any payment is sent — a call priced above it is declined, not charged. Total exposure is otherwise the wallet balance — keep it small. - Every paid call goes through a quote first:
databroker_fetchanddatabroker_batch_createnever spend money unless called again withconfirm: true. - On top of that, when the connected client advertises MCP elicitation support, every payment also requires a human to explicitly accept a prompt sent by the server itself, naming the exact URL and USDC amount — enforced in code (
confirmWithHumaninlib.ts), not left to the calling model's judgement. On clients without elicitation support this extra check is skipped (seeDATABROKER_REQUIRE_ELICITATIONbelow if you'd rather it fail closed instead).
Env vars
| Var | Required | Default | Notes |
|---|---|---|---|
DATABROKER_BASE_URL |
yes | — | e.g. https://api.databroker.mossforge.dev |
DATABROKER_SIGNER |
no | raw |
raw or cdp — see Who holds the wallet |
DATABROKER_WALLET_KEY |
yes, if SIGNER=raw |
— | 0x-prefixed private key |
CDP_API_KEY_ID |
yes, if SIGNER=cdp |
— | Coinbase CDP API key id |
CDP_API_KEY_SECRET |
yes, if SIGNER=cdp |
— | Coinbase CDP API key secret |
CDP_WALLET_SECRET |
yes, if SIGNER=cdp |
— | Coinbase CDP wallet secret |
DATABROKER_MAX_USDC |
no | 0.50 |
Per-call spend cap, enforced regardless of signer |
DATABROKER_REQUIRE_ELICITATION |
no | false |
If true, block paid calls on clients that don't advertise MCP elicitation support, instead of falling back to confirm: true alone |
Preguntas sobre databroker MCP
¿Cómo agrego databroker MCP a Claude Code?
Ejecuta claude mcp add --env 'DATABROKER_BASE_URL=<DATABROKER_BASE_URL>' --env 'CDP_API_KEY_ID=<YOUR_CDP_API_KEY_ID>' --env 'CDP_API_KEY_SECRET=<YOUR_CDP_API_KEY_SECRET>' --env 'CDP_WALLET_SECRET=<YOUR_CDP_WALLET_SECRET>' --env 'DATABROKER_WALLET_KEY=<YOUR_DATABROKER_WALLET_KEY>' databroker -- npx -y @mossforge/databroker-mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego databroker MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona databroker MCP?
Expone 6 herramientas, incluidas databroker_discover, databroker_fetch, databroker_meta, databroker_health, databroker_batch_create.
¿Existe un límite de cuánto se puede gastar por consulta?
Sí, cada consulta pagada está limitada por la variable de entorno DATABROKER_MAX_USDC, que tiene un valor predeterminado de 0.50 USDC.
¿Necesito ETH para pagar las transacciones?
No, solo necesitas fondear tu wallet con USDC en la mainnet de Base, ya que las transferencias EIP-3009 no requieren gas para el pagador.