CoverBureau
REMOTE · COVERBUREAU.COM
Checks certificates of insurance (ACORD 25) against your requirements. Pay per call, x402 USDC.
Available components
Last scanned (9 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 444 tokens (~148/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 30 Oct 26 +3
- Stability: fail → pass ▲ security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 76.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 66 to 69.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 56 to 63.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 46 to 56.
- 7 Oct 26 0
- Schema quality: pass → fail ▼ functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 32 to 36.
- 30 Sept 26 0
- Stability: 0.40 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “check_carrier” rewrote its description, which is the text the model reads security
- Schema quality: 63 → 109 ▼ functional
- “check_carrier” made “state” required, so existing callers break ▼ functional
- Tool coverage: 0% → 78% ▲ functional
- Schema quality: fair → good functional
- “check_carrier” reworded the description of “carrierName” cosmetic
- “check_carrier” reworded the description of “minRating” cosmetic
- “check_carrier” reworded the description of “naic” cosmetic
- “check_carrier” reworded the description of “state” cosmetic
- “extract_coi” reworded the description of “document” cosmetic
- “validate_coi” reworded the description of “document” cosmetic
- “validate_coi” reworded the description of “requirements” cosmetic
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 5 Nov 2026 · Probed https://coverbureau.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=coverbureau.com | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 74463dbda52bc58f0e9458d48567c4ac |
| SANs: coverbureau.com | ||||||
| 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 insecure
Validation of coverbureau.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| coverbureau.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://coverbureau.com/mcp | Verified | 200 | |
| http (plaintext) | http://coverbureau.com/mcp | Inconclusive | 404 |
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 →
check_carrier Check Carrier ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| carrierName | – | – | Carrier name as printed on the certificate |
| minRating | – | – | Minimum acceptable A.M. Best rating, e.g. "A- VII". Defaults to "A- VII" |
| naic | – | – | 5-digit NAIC company code, e.g. "25623" |
| state | string | yes | 2-letter US state code, e.g. "NY" — REQUIRED |
No output schema declared.
No examples provided.
extract_coi Extract COI ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document | – | – | The certificate to read: base64 bytes, or an https url fetched server-side (§3.5) |
| options | object | – | – |
No output schema declared.
No examples provided.
validate_coi Validate COI ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document | – | – | The certificate to read: base64 bytes, or an https url fetched server-side (§3.5) |
| options | object | – | – |
| requirements | – | – | Either an inline RequirementProfile (§4.2) or { profileId } naming a stored profile (§3.2) |
No output schema declared.
No examples provided.
How do I install the CoverBureau MCP server?
CoverBureau is a hosted endpoint at https://coverbureau.com/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 · coverbureau.com
claude mcp add --transport http com-coverbureau-mcp 'https://coverbureau.com/mcp'
What is the CoverBureau MCP server?
CoverBureau is an MCP server listed in the public MCP registry as com.coverbureau/mcp. Checks certificates of insurance (ACORD 25) against your requirements. Pay per call, x402 USDC. This page covers its hosted endpoint (https://coverbureau.com/mcp).
Is the CoverBureau MCP server safe to use?
CoverBureau scores 73 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 CoverBureau MCP server expose?
CoverBureau exposes 3 tools: extract_coi, check_carrier, validate_coi. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.
Does the CoverBureau MCP server require authentication?
No. We connected to CoverBureau without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CoverBureau MCP server still maintained?
CoverBureau is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.