CoverBureau MCP Server
Official remote MCP server (JSON-RPC 2.0 over HTTP POST) from CoverBureau that reads US ACORD 25 Certificates of Insurance, judges them against caller-supplied requirements, and returns Ed25519-signed verdicts. Paid per call via x402 (USDC on Base mainnet); no account or API key.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
extract_coi— Read an ACORD 25 Certificate of Insurance into structured data (spec §3.1). Returns a signed envelope. Use it when you want the fields and will apply your own rules; for a verdict against requirements you supply use validate_coi instead - it extracts as part of its work, so calling both on one document pays for the same read twice.check_carrier— Check an insurer by NAIC code or name: known, licensed, and adequately rated (spec §3.3). Provide at least one of naic or carrierName, plus state (required). Answers from an UNVERIFIED seed dataset (§4.5 datasetStatus) and returns a signed envelope. Needs no document. Use it when you have a carrier but no certificate; validate_coi already checks the carrier when you do.validate_coi— Extract an ACORD 25 certificate AND judge it against a requirement profile (inline or profileId), returning a signed Verdict with per-check results, flags, and a risk score (spec §3.2). Use extract_coi instead if you only want the fields without a verdict; use check_carrier only when you have no certificate, since this tool already checks the carrier when your profile sets a carrier requirement.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.