io.github.peter-schout/bol-ai
REMOTE · BOL.AI · SCANNED SEP 20
Extract structured data from Bills of Lading: parties, ports, containers, incoterms. EU-hosted.
Available components
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. How we score → Why this is hard to score →
Endpoint Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 727 tokens (~90/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.peter-schout/bol-ai MCP server?
io.github.peter-schout/bol-ai is a hosted endpoint at https://bol.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bol.ai
claude mcp add --transport http peter-schout-bol-ai 'https://bol.ai/api/mcp'
{
"mcpServers": {
"peter-schout-bol-ai": {
"url": "https://bol.ai/api/mcp"
}
}
} {
"servers": {
"peter-schout-bol-ai": {
"type": "http",
"url": "https://bol.ai/api/mcp"
}
}
} [mcp_servers.peter-schout-bol-ai] url = "https://bol.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"peter-schout-bol-ai": {
"type": "remote",
"url": "https://bol.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add peter-schout-bol-ai --url 'https://bol.ai/api/mcp' --transport streamable-http
mcp_servers:
peter-schout-bol-ai:
url: "https://bol.ai/api/mcp" {
"McpServers": {
"peter-schout-bol-ai": {
"Transport": "http",
"Url": "https://bol.ai/api/mcp"
}
}
} assistant mcp add peter-schout-bol-ai -t streamable-http -u 'https://bol.ai/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://bol.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bol.ai | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 346dc5c6e6ca5d11136eb189885cb9b2 |
| SANs: bol.ai, www.bol.ai, *.www.bol.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of bol.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| bol.ai. | present | 2371 | 13 | Verified |
| bol.ai. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Provide Authorization: Bearer bolai_... or sign in at https://bol.ai/app/", resource_metadata="https://bol.ai/.well-known/oauth-protected-resource/api/mcp"
Bearer error="invalid_token", error_description="Provide Authorization: Bearer bolai_... or sign in at https://bol.ai/app/", resource_metadata="https://bol.ai/.well-known/oauth-protected-resource/api/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' https://static.cloudflareinsights.com https://analytics.ahrefs.com; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data:; connect-src 'self' https://cloudflareinsights.com https://analytics.ahrefs.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), tools=(self) |
Protected resource metadata
| Document | https://bol.ai/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://bol.ai/api/mcp |
| Authorisation server | https://bol.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bol.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://bol.ai/api/mcp | HTTPS enforced | 301 | https://bol.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export_documents Export documents as normalized rows ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rows | number | – | Maximum rows to return (default 500) |
| type | string | – | Only include documents of this type |
No output schema declared.
No examples provided.
extract_batch Extract multiple freight documents ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | URLs of documents to fetch and extract (max 10) |
No output schema declared.
No examples provided.
extract_bol Extract freight document ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_document Get extraction result ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Document id |
No output schema declared.
No examples provided.
get_related_documents Reconcile shipment documents ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Document id to reconcile against the rest of the account |
No output schema declared.
No examples provided.
get_usage Check credits and subscription ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_documents List documents ~38
List the 100 most recent documents for this account with id, filename, status (pending/done/failed), doc_type and primary reference number.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
save_corrections Save field corrections ~79
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).
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Complete corrected fields object, including doc_type |
| id | string | yes | Document id |
No output schema declared.
No examples provided.
What is the io.github.peter-schout/bol-ai MCP server?
io.github.peter-schout/bol-ai is an MCP server listed in the public MCP registry as io.github.peter-schout/bol-ai. Extract structured data from Bills of Lading: parties, ports, containers, incoterms. EU-hosted. This page covers its hosted endpoint (https://bol.ai/api/mcp).
Is the io.github.peter-schout/bol-ai MCP server safe to use?
io.github.peter-schout/bol-ai scores 95 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.peter-schout/bol-ai MCP server expose?
io.github.peter-schout/bol-ai exposes 8 tools: extract_bol, extract_batch, list_documents, get_document, save_corrections, and 3 more. Their descriptions and schemas cost roughly 700 tokens of context every time the server is loaded.
Does the io.github.peter-schout/bol-ai MCP server require authentication?
Yes. io.github.peter-schout/bol-ai asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.peter-schout/bol-ai MCP server still maintained?
io.github.peter-schout/bol-ai is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.