# io.github.peter-schout/bol-ai (remote · bol.ai)

Extract structured data from Bills of Lading: parties, ports, containers, incoterms. EU-hosted.

- Trust score: 83/100 (high trust)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `bol.ai`: 83/100 (this document), [markdown](https://verifymcp.io/servers/peter-schout-bol-ai/api-mcp.md), [page](https://verifymcp.io/servers/peter-schout-bol-ai/api-mcp)

## Channel facts

- Endpoint: `https://bol.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 100/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 727 tokens (~90/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http peter-schout-bol-ai https://bol.ai/api/mcp
```

### Codex

```toml
[mcp_servers.peter-schout-bol-ai]
url = "https://bol.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "peter-schout-bol-ai": {
      "type": "remote",
      "url": "https://bol.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add peter-schout-bol-ai --url https://bol.ai/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  peter-schout-bol-ai:
    url: "https://bol.ai/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "peter-schout-bol-ai": {
      "type": "http",
      "url": "https://bol.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 82, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 76, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 75)

First indexed and scored.

## MCP tools (8)

### `extract_bol` (~146 tokens)

Extract freight document

Extract structured data from a freight document (PDF, PNG or JPG, max 10 MB): Bill of Lading, commercial invoice, packing list, or CMR road waybill. The document type is detected automatically and returned as `doc_type`. Provide either a fetchable `url` or `base64` file content. Fields not present in the document are null — never guessed. Each successful extraction bills one document.

Input parameters:

- `base64` (string): Base64-encoded file content (alternative to url)
- `filename` (string): Filename including extension, e.g. shipment-4711.pdf
- `url` (string): URL of the document to fetch and extract

### `extract_batch` (~79 tokens)

Extract multiple freight documents

Extract up to 10 freight documents in one call. Provide an array of fetchable URLs; each document is processed and billed independently, and the response reports a per-document outcome so partial success (e.g. running out of credits mid-batch) is explicit.

Input parameters:

- `urls` (array, required): URLs of documents to fetch and extract (max 10)

### `list_documents` (~38 tokens)

List documents

List the 100 most recent documents for this account with id, filename, status (pending/done/failed), doc_type and primary reference number.

### `get_document` (~84 tokens)

Get extraction result

Get the extraction result for a document by id: doc_type, extracted fields, user corrections (when present), and deterministic verification warnings (ISO 6346 container check digits, plausibility flags). `fields` is the best available data (corrections win); `original_fields` and `corrected_fields` show both sides.

Input parameters:

- `id` (string, required): Document id

### `save_corrections` (~79 tokens)

Save field corrections

Save corrected field values for an extracted document. The original extraction is kept alongside the corrections; corrected data takes precedence in get_document, exports and reconciliation. Pass the complete corrected fields object (same shape as returned by get_document).

Input parameters:

- `fields` (object, required): Complete corrected fields object, including doc_type
- `id` (string, required): Document id

### `get_related_documents` (~116 tokens)

Reconcile shipment documents

Cross-document reconciliation: find the other documents in this shipment (linked by shared reference numbers such as B/L number and invoice number) and compare them field by field — shipper/seller and consignee/buyer names, total gross weight (5% tolerance) and package counts. Returns matches and mismatches per linked document. Catches the discrepancies that cause customs holds, amended entries and demurrage. Deterministic — no extra document billed.

Input parameters:

- `id` (string, required): Document id to reconcile against the rest of the account

### `export_documents` (~103 tokens)

Export documents as normalized rows

Export completed extractions as TMS/ERP-ready normalized line rows (one row per container / invoice line / package / goods line), newest first. Optional doc_type filter and max_rows cap. Corrected data wins over the original extraction. For CSV/XLSX files use GET /api/bol/export on the REST API.

Input parameters:

- `max_rows` (number): Maximum rows to return (default 500)
- `type` (string): Only include documents of this type

### `get_usage` (~55 tokens)

Check credits and subscription

Check this account's remaining prepaid credits and subscription status. Call this before large batches to avoid running out of credits mid-workflow. When the account cannot bill more documents, a human can top up at the returned buy_credits_url.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/peter-schout-bol-ai/api-mcp#diagnostics

## Score history

- 2026-08-03: 83
- 2026-08-02: 83
- 2026-08-01: 82
- 2026-07-31: 82
- 2026-07-30: 76
- 2026-07-29: 77
- 2026-07-28: 77
- 2026-07-27: 76
- 2026-07-26: 75

## Links

- Remote endpoint: https://bol.ai/api/mcp
- Authorisation metadata: https://bol.ai/.well-known/oauth-protected-resource/api/mcp
- Website: https://bol.ai/
- Changelog RSS feed: https://verifymcp.io/servers/peter-schout-bol-ai/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/peter-schout-bol-ai/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/peter-schout-bol-ai/api-mcp