CoverBureau MCP server
com.coverbureau/mcpcoverbureau.comstreamable-httpv1.0.0Scanned
Checks certificates of insurance (ACORD 25) against your requirements. Pay per call, x402 USDC.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CoverBureau MCP server can do
The CoverBureau MCP server is published by coverbureau.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: check_carrier), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (base64-blob). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
check_carrierCheck an insurer by NAIC code or name: known, licensed, and adequately rated (spec §3.3).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
extract_coiRead an ACORD 25 Certificate of Insurance into structured data (spec §3.1).No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
validate_coiExtract 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 findings
Why it is in this group
- The name "validate_coi" says "validate": a word for reading.
Findings
- Warn
The input schema at properties.requirements.anyOf[0].properties.certificateHolderMustMatch.$ref contains a 64-character base64 string.
What this check looks forMatched text
inputSchema.properties.requirements.anyOf[0].properties.certificateHolderMustMatch.$ref: "#/properties/requirements/anyOf/0/properties/insuredNameMustMatch"
- Warn
The input schema at properties.requirements.anyOf[0].properties.coverages.properties.autoLiability.$ref contains a 81-character base64 string.
What this check looks forMatched text
inputSchema.properties.requirements.anyOf[0].properties.coverages.properties.autoLiability.$ref: "#/properties/requirements/anyOf/0/properties/coverages/properties/gen..."
- Warn
The input schema at properties.requirements.anyOf[0].properties.coverages.properties.umbrellaExcess.$ref contains a 81-character base64 string.
What this check looks forMatched text
inputSchema.properties.requirements.anyOf[0].properties.coverages.properties.umbrellaExcess.$ref: "#/properties/requirements/anyOf/0/properties/coverages/properties/gen..."
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://coverbureau.com/mcp: tools/list returned 3 tools to an anonymous client, including check_carrier (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnvalidate_coi
The input schema at properties.requirements.anyOf[0].properties.certificateHolderMustMatch.$ref contains a 64-character base64 string.
What this check looks forMatched text
inputSchema.properties.requirements.anyOf[0].properties.certificateHolderMustMatch.$ref: "#/properties/requirements/anyOf/0/properties/insuredNameMustMatch"
- Warnvalidate_coi
The input schema at properties.requirements.anyOf[0].properties.coverages.properties.autoLiability.$ref contains a 81-character base64 string.
What this check looks forMatched text
inputSchema.properties.requirements.anyOf[0].properties.coverages.properties.autoLiability.$ref: "#/properties/requirements/anyOf/0/properties/coverages/properties/gen..."
- Warnvalidate_coi
The input schema at properties.requirements.anyOf[0].properties.coverages.properties.umbrellaExcess.$ref contains a 81-character base64 string.
What this check looks forMatched text
inputSchema.properties.requirements.anyOf[0].properties.coverages.properties.umbrellaExcess.$ref: "#/properties/requirements/anyOf/0/properties/coverages/properties/gen..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http coverbureau https://coverbureau.com/mcpclaude mcp add --transport http coverbureau https://coverbureau.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__coverbureau__extract_coi",
"mcp__coverbureau__validate_coi"
],
"ask": [
"mcp__coverbureau__check_carrier"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as coverbureau. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.coverbureau/mcp/verify?hash=76125b857e937f7f84e303cb952866a4d157599a9570de7e0a79a5951d5c3310" | jq -e '.changed == false'Pinned hash 76125b857e93, from Nov 12, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.coverbureau/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.coverbureau/mcp)Source: MCP Registry. Synced Oct 21, 2026, 17:53 UTC.
CoverBureau MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CoverBureau MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CoverBureau MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CoverBureau MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CoverBureau MCP server have?
- 3 tools: 1 write, 2 read. check_carrier, extract_coi and validate_coi.
Does the CoverBureau MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CoverBureau MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CoverBureau MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.