AI Agent Liability Insurance
REMOTE · JOHALINSURANCEBROKERS.COM
Quote AI agent liability insurance (Tech E&O + AI coverage) from a licensed US insurance broker.
Available components
Last scanned (50 minutes ago)
Scores higher than 54% 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 583 tokens (~291/item across 2 items; 2 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% 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 2 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 67
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 5 Nov 2026 · Probed https://johalinsurancebrokers.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=johalinsurancebrokers.com | CN=YR1,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | RSA 2048 | SHA256-RSA | 5133d40c646b8ed77dc0aa69b6dabf8736a |
| SANs: johalinsurancebrokers.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of johalinsurancebrokers.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| johalinsurancebrokers.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://johalinsurancebrokers.com/mcp | Verified | 200 | |
| http (plaintext) | http://johalinsurancebrokers.com/mcp | HTTPS enforced | 308 | https://johalinsurancebrokers.com/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 →
get_ai_liability_coverage_info AI agent liability insurance — what's covered ~71
Describes the AI agent liability insurance Johal Insurance Brokers (licensed US broker) can quote: Technology E&O with affirmative AI coverage for companies that build or deploy AI agents. Returns coverages, limits, eligible states, required quote fields and how binding works. Free, no side effects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_ai_liability_quote Request an AI agent liability insurance quote ~463
Submits a quote request for AI agent liability insurance (Tech E&O + AI coverage) for a US company headquartered in CA, TX, IL, WI, LA. A licensed broker rates it and emails the quote to the company contact, usually the same business day. Free. Each call creates a real quote request that a human broker works on, using the company details provided. It does not bind coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_agentic_tier | string | yes | How autonomously the AI acts. |
| ai_company_type | string | – | – |
| ai_coverage_options | array | – | AI coverage parts wanted (default: all). |
| ai_governance_controls | array | – | – |
| ai_high_stakes_domains | array | – | – |
| ai_model_providers | array | – | – |
| ai_sublimit | number | – | AI coverage sublimit (default 1000000; cannot exceed limit). |
| ai_training_approach | string | – | – |
| annual_revenue | number | yes | Annual gross revenue in USD (estimate is fine). |
| city | string | – | – |
| company_name | string | yes | Legal name of the company to be insured. |
| contact_email | string | yes | Email the quote is sent to. |
| contact_name | string | yes | Name of the human at the company who will receive the quote. |
| contact_phone | string | – | – |
| current_insurance | string | – | Current Tech E&O / cyber carrier and expiration date, if any. |
| limit | number | – | Tech E&O limit wanted (default 1000000). |
| notes | string | – | – |
| prior_claims | boolean | – | Any Tech E&O or AI-related claims, regulatory actions or cease-and-desist letters in the last 3 years? |
| requested_by_agent | string | – | Name of the AI agent or platform submitting this request. |
| retention | number | – | Retention / deductible per claim (default 10000). |
| state | string | yes | State of the company's headquarters. |
| street | string | – | – |
| website | string | – | Company website. |
| what_the_product_does | string | – | Plain description of the product and what the AI/agent does for customers. |
| zip | string | – | – |
No output schema declared.
No examples provided.
How do I install the AI Agent Liability Insurance MCP server?
AI Agent Liability Insurance is a hosted endpoint at https://johalinsurancebrokers.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 · johalinsurancebrokers.com
claude mcp add --transport http com-johalinsurancebrokers-ai-liability-insurance 'https://johalinsurancebrokers.com/mcp'
What is the AI Agent Liability Insurance MCP server?
AI Agent Liability Insurance is an MCP server listed in the public MCP registry as com.johalinsurancebrokers/ai-liability-insurance. Quote AI agent liability insurance (Tech E&O + AI coverage) from a licensed US insurance broker. This page covers its hosted endpoint (https://johalinsurancebrokers.com/mcp).
Is the AI Agent Liability Insurance MCP server safe to use?
AI Agent Liability Insurance scores 69 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 AI Agent Liability Insurance MCP server expose?
AI Agent Liability Insurance exposes 2 tools: get_ai_liability_coverage_info, request_ai_liability_quote. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.
Does the AI Agent Liability Insurance MCP server require authentication?
No. We connected to AI Agent Liability Insurance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Agent Liability Insurance MCP server still maintained?
AI Agent Liability Insurance 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.