Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Insuro

REMOTE · MCP.INSURO.COM.AU · SCANNED SEP 24

Free insurance vault MCP: OAuth policies, renewals, coverage Q&A, file PDFs. Global; not advice.

+4 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security69
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 713 tokens (~118/item across 6 items; 6 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 Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the Insuro MCP server?

Insuro is a hosted endpoint at https://mcp.insuro.com.au/, 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 · mcp.insuro.com.au

# add to Claude Code
claude mcp add --transport http au-com-insuro-insuro 'https://mcp.insuro.com.au/'
// .cursor/mcp.json
{
  "mcpServers": {
    "au-com-insuro-insuro": {
      "url": "https://mcp.insuro.com.au/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "au-com-insuro-insuro": {
      "type": "http",
      "url": "https://mcp.insuro.com.au/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.au-com-insuro-insuro]
url = "https://mcp.insuro.com.au/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "au-com-insuro-insuro": {
      "type": "remote",
      "url": "https://mcp.insuro.com.au/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add au-com-insuro-insuro --url 'https://mcp.insuro.com.au/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  au-com-insuro-insuro:
    url: "https://mcp.insuro.com.au/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "au-com-insuro-insuro": {
      "Transport": "http",
      "Url": "https://mcp.insuro.com.au/"
    }
  }
}
# add to Vellum
assistant mcp add au-com-insuro-insuro -t streamable-http -u 'https://mcp.insuro.com.au/'
// mcp.json
{
  "mcpServers": {
    "au-com-insuro-insuro": {
      "type": "http",
      "url": "https://mcp.insuro.com.au/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 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.

Diagnostics

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 24 Sept 2026 · Probed https://mcp.insuro.com.au

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=insuro.com.au CN=WE1,O=Google Trust Services,C=US 30 Aug 2026 29 Nov 2026 ECDSA 256 ECDSA-SHA256 9097465dc99ff50b0e46792406a4d0e0
SANs: insuro.com.au, *.insuro.com.au
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 mcp.insuro.com.au. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
au. present 26642 8 Verified
com.au. present 14185 8 Verified
insuro.com.au. 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=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.insuro.com.au Verified 200
http (plaintext) http://mcp.insuro.com.au Inconclusive 401
MCP tools · 6 exposed · ~638 tokens

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 →

Tool Tokens
add_policy ~193

Manually create a user-entered policy in the same table as the website form. Requires insurer and type. Policy number, renewal/expiry, start date, and premium are optional. Requires vault.write. Insuro does not sell insurance or give financial advice.

NameTypeReqDescription
expirystringAlias for renewal_date.
insurerstringyesInsurer / provider name.
namestringDisplay name. Defaults to insurer + type.
numberstringPolicy number if known.
premiumnumberPremium amount, optional.
premium_frequencystringe.g. yearly, monthly.
renewal_datestringRenewal date YYYY-MM-DD.
start_datestringStart date YYYY-MM-DD.
typestringyesPolicy type: home, auto, health, life, tpd, income_protection, travel, other (car maps to auto).

No output schema declared.

No examples provided.

ask_coverage ~107

Ask a natural-language coverage question about the connected vault (same assistant as the Insuro website). Optional policy_id hint from list_policies. Returns a short answer, which policy/document was used, and a financial-advice disclaimer. Never returns PDS text or document bodies. Requires vault.read.

NameTypeReqDescription
policy_idstringOptional policy to focus on (from list_policies).
questionstringyesNatural-language coverage question, e.g. "Am I covered for flood?"

No output schema declared.

No examples provided.

get_renewals ~57

Policies renewing within a window. Optional input { days?: number }, default 90. Same summary fields as list_policies — no document bodies.

NameTypeReqDescription
daysintegerLook-ahead window in days. Defaults to 90.

No output schema declared.

No examples provided.

get_vault ~59

Read-only summary of the connected Insuro vault. Returns the private @insuro.com.au vault email, the account email, how many policies are on file, and upcoming renewal dates. Does not return documents, PDS text, or policy numbers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ingest_document ~169

File a policy PDF into the vault. Send the file as content_base64 (standard base64, optional data: URL). Same storage, inbox, and parse path as the website. Links to a matching policy when the parser can; otherwise lands in the inbox. Returns a structured summary only — never PDS text. Max decoded size 4MB (Streamable HTTP limit). Requires vault.write.

NameTypeReqDescription
blobstringAlias for content_base64.
content_base64stringFile bytes as standard base64. data:application/pdf;base64,... is accepted.
filenamestringyesOriginal filename, e.g. nrma-car.pdf
mime_typestringDefaults to application/pdf.
policy_idstringOptional policy to link when already known.

No output schema declared.

No examples provided.

list_policies ~53

Read-only summaries of policies in the connected vault: type, insurer/provider, policy number (if present), status, and renewal/start dates. Does not return PDS text, document bodies, notes, or coverage wording.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Insuro MCP server?

Insuro is an MCP server listed in the public MCP registry as au.com.insuro/insuro. Free insurance vault MCP: OAuth policies, renewals, coverage Q&A, file PDFs. Global; not advice. This page covers its hosted endpoint (https://mcp.insuro.com.au).

Is the Insuro MCP server safe to use?

Insuro scores 79 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 Insuro MCP server expose?

Insuro exposes 6 tools: get_vault, list_policies, get_renewals, ask_coverage, ingest_document, add_policy. Their descriptions and schemas cost roughly 638 tokens of context every time the server is loaded.

Does the Insuro MCP server require authentication?

No. We connected to Insuro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Insuro MCP server still maintained?

Insuro is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.