MCP.Market

Databroker MCP server

by mossforge.dev·dev.mossforge/databroker·v0.5.0

Pay-per-call UK MOT history, reliability analytics and identifier utilities. x402 USDC on Base.

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
New

0 stars63 downloads/wk

Reviews

Write one

Nobody has reviewed Databroker yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Databroker tools (6, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • databroker_batch_createwrite action
  • databroker_batch_status

    Poll the status of a batch job created by databroker_batch_create. FREE call - no payment made (payment already happened at job creation). Returns per-key state: "complete" (data included inline), "pending" (still fetching - poll again shortly), or "not_found" (valid key, no record exists - this is a final result, not an error). Jobs expire 24 hours after creation. Args: - jobId (string): The job_

  • databroker_discover

    List the currently enabled DataBroker datasets, their USDC prices, and descriptions. FREE call - no payment made. Always call this first if you don't know which dataset id to use, or what a call will cost. Each entry includes a "kind": "cached" (per-entity data backed by an ingestor/pipeline, e.g. "dvsa-mot" or "dvsa-mot-analytics"), "computed" (a pure deterministic function, no caching, never sta

  • databroker_fetch
  • databroker_health

    Check whether the DataBroker API is up. FREE call - no payment made, always returns 200 when the service is healthy.

  • databroker_meta

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 61 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Databroker compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,243 servers
Tools
6
the typical server has 7
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
63
more than 49% of 12,306 servers with a package

What its tools let an agent do: 5 read · 1 change

Install Databroker in Claude Code, Cursor or VS Code

Runs npx -y @mossforge/databroker-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add databroker -- npx -y @mossforge/databroker-mcp
Add to Cursor

What the publisher says

From the Databroker repository's README, as published. We do not edit it. Read it on GitHub

Mossforge DataBroker

Pay-per-call UK data and utility API, gated by x402 micropayments on Base mainnet. No API keys, no accounts, no subscriptions — send a signed USDC payment with your HTTP request and get an answer back in the same response cycle.

llms.txt · openapi.yaml

  • Base URL: https://api.databroker.mossforge.dev
  • Network: Base mainnet (eip155:8453)
  • Payment token: USDC
  • Protocol: x402, exact scheme
  • Landing / docs: databroker.mossforge.dev ·

Quick start

curl https://api.databroker.mossforge.dev/v1/discover

/v1/discover is free and returns every enabled dataset with its current price, description, and provenance (kind, implemented standard, deterministic, data_source). Prices are configured server-side and can change — always trust the live 402 challenge over anything written in this README.

Requesting any paid route without payment returns HTTP 402 with the exact amount, recipient, and network in a PAYMENT-REQUIRED header. Sign an EIP-3009 USDC transfer authorization, retry with a PAYMENT-SIGNATURE header, and the API verifies, settles on-chain, and returns the data with a PAYMENT-RESPONSE receipt. A 402 means no funds have moved — you only pay on a 200.

x402 client libraries: @x402/fetch (TypeScript), x402 (Python), x402-go (Go).

Use it from an agent

MCP server

@mossforge/databroker-mcp gives any MCP client (Claude Desktop, Claude Code, Cursor) pay-per-call access to everything below, with x402 payment handled for it. No build step:

{
  "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"
      }
    }
  }
}

Or for Claude Code:

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

Payment is never automatic. databrokerfetch and databrokerbatchcreate return a price quote first and spend nothing until called again with confirm: true enforced in the server, not left to the model's judgement. Every paid call is additionally capped by DATABROKERMAX_USDC; anything priced above the cap is declined before payment. See mcp-server/ for signer options (self-custodied key or Coinbase CDP) and security notes.

Agent skills

Three OpenClaw skills in skills/, scoped by tier - mossforge-mot-history (single vehicle), mossforge-mot-analytics (fleet statistics), mossforge-data-utilities (24 identifier/geo/reference endpoints).

Direct HTTP

Worked examples in examples/ for Python and TypeScript, both as a plain fetch and as an agent tool definition.

Endpoints

All paid routes follow the same shape: GET /v1/{dataset_id}/{key}. Keys are URL-decoded server-side, so percent-encode anything containing /, spaces, or + (e.g. 205/55R16 91V → /v1/util-tyre-size/205%2F55R16%2091V).

Free routes

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Databroker: common questions

Is Databroker MCP server safe?
Mostly: it is graded B (77/100). Read the Databroker safety report
How do I install Databroker?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Databroker need an API key?
Yes. The registry entry asks for DATABROKER_WALLET_KEY, CDP_API_KEY_ID, CDP_API_KEY_SECRET, CDP_WALLET_SECRET.
Is Databroker maintained?
The last commit was 67 days ago (2026-08-30). The latest release is v0.5.0.
How does Databroker compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.