Bol AI is listed as active in the registry but did not answer our last check. It exposes 8 tools.
Extract structured data from Bills of Lading: parties, ports, containers, incoterms. EU-hosted.
Uptime history
52 days of history · worst day 92%
52 days agonow
95.6%
Uptime 24h
87 of 91 checks
8
Tools
read from the server
390 ms
Response time
average over 24h
open, no key
Access
streamable-http
Bol AI does not always answer
Over the last week it answered 98.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
run in your terminal
claude mcp add bol-ai --transport http https://bol.ai/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"bol-ai": {
"url": "https://bol.ai/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.bol-ai]
url = "https://bol.ai/api/mcp".cursor/mcp.json
{
"mcpServers": {
"bol-ai": {
"url": "https://bol.ai/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"bol-ai": {
"url": "https://bol.ai/api/mcp"
}
}
}Available tools 8
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
extract
extract_batch
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.
extract_bol
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.
document
get_document
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.
documents
list_documents
List the 100 most recent documents for this account with id, filename, status (pending/done/failed), doc_type and primary reference number.
export
export_documents
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.
related
get_related_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.
save
save_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).
usage
get_usage
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://bol.ai/api/mcp | streamable-http | answering | 8243 ms | 11 min ago |
Alternatives to Bol AI
same job, measured the same waySuparse Document Processing
by suparse
Extract structured data from PDFs and documents with Suparse AI OCR.
Firecrawl
by mcparmory
Scrape, crawl, and extract structured data from websites at scale
DataSnipe MCP
by datasnipe
Extract structured data points from research papers and other documents with an LLM.
Extend
by extend
Turn documents into structured data: parse, extract, classify, split, and fill PDF forms.
Document Parser
by agenson-horrowitz
Parse and extract structured data from various document formats (PDF, Word, HTML).
Talonic
by talonicdev
Extract structured, schema-validated data from PDFs, scans, images, spreadsheets, and forms.
Strings-LE
by nolindnaidoo
Extract string values from config files, data files and plain text.
Saas Pricing Extractor
by dataleadspro
Extract and structure pricing pages from any SaaS site: plans, tiers, and features.
Bol AI — questions
Answers built from our own checks of this server.
What can Bol AI do?
It exposes 8 tools, read directly from the server on our last check. Among them: export_documents, extract_batch, extract_bol, get_document, get_related_documents, get_usage and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Bol AI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 87 of 91 checks got a reply (95.6%), average response time 390 ms. The bar chart above shows every period we have measured.
The registry lists Bol AI as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Bol AI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Bol AI need an API key?
No. Bol AI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Bol AI?
It answers our handshake in 390 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.