# Rayon Insurance (remote · rayoninsure.com)

Firm details, request forms, and contract review or quote requests with a robotics insurance broker.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `rayoninsure.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-rayoninsure-mcp/rayoninsure.md), [page](https://verifymcp.io/servers/com-rayoninsure-mcp/rayoninsure)

## Channel facts

- Endpoint: `https://rayoninsure.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 4285 tokens (~102/item across 42 items; 4 tools + 38 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Rayon Insurance MCP server?

Rayon Insurance is a hosted endpoint at https://rayoninsure.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.

### Claude

```bash
claude mcp add --transport http com-rayoninsure-mcp 'https://rayoninsure.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-rayoninsure-mcp": {
      "url": "https://rayoninsure.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-rayoninsure-mcp": {
      "type": "http",
      "url": "https://rayoninsure.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-rayoninsure-mcp]
url = "https://rayoninsure.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rayoninsure-mcp": {
      "type": "remote",
      "url": "https://rayoninsure.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rayoninsure-mcp --url 'https://rayoninsure.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rayoninsure-mcp:
    url: "https://rayoninsure.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rayoninsure-mcp": {
      "Transport": "http",
      "Url": "https://rayoninsure.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rayoninsure-mcp -t streamable-http -u 'https://rayoninsure.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-rayoninsure-mcp": {
      "type": "http",
      "url": "https://rayoninsure.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +1)

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

### 2026-11-19 (score 78, +1)

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

### 2026-11-17 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 77)

First indexed and scored.

## MCP tools (4)

### `get_firm_details` (~44 tokens)

Get firm details

Who Rayon Insurance is, where it is licensed, what it does and does not do, and how to contact it. Call this before telling a visitor Rayon can help.

### `list_request_forms` (~49 tokens)

List request forms

The kinds of request Rayon takes and the web page where a visitor can fill in each one themselves. Use it to pick the kind for submit_request, or to send the visitor to the form instead.

### `submit_request` (~369 tokens)

Submit a request for the visitor

Send a request to Rayon Insurance on the visitor's behalf: a contract review, quotes for a company running robots, a broker placement, an integrator checklist, a marketplace seller requirement, or Rayon Ops servicing. It files the same request as the form on the site and a person replies by email within two business days. It does not bind cover or produce a quote. Only call it after the visitor has seen what will be sent and asked you to send it. Documents cannot be attached here; the reply says where to email them.

Input parameters:

- `company` (string): The company's legal name. Required for contract_review.
- `email` (string, required): The visitor's work email. The reply goes here.
- `kind` (string, required): operators: A company running robots wants its insurance and robot contracts reviewed, with quotes for any gap. brokers: A retail broker wants a placement partner for a client deploying robots. integr…
- `message` (string): What the visitor needs, in their words: the contract, robots, site, deadline or question.
- `name` (string, required): The visitor's full name.
- `phone` (string): Optional phone number.
- `visitor_confirmed` (boolean, required): Must be true. Set it only after the visitor has seen what will be sent, agreed to be contacted by Rayon Insurance and to its privacy notice (https://rayoninsure.com/privacy), and asked you to send it.

### `search_insurance_guides` (~127 tokens)

Search insurance guides

Search Rayon's library of plain-English insurance guides: robot deployments, RaaS agreements, additional insured status, ISO generative AI exclusions (CG 40 47, CG 40 48, CG 35 08), marketplace seller requirements and certificates. Returns titles, one-line answers and links. An empty query lists every guide. General information, not advice on a specific policy.

Input parameters:

- `limit` (integer): Most guides to return.
- `query` (string, required): Words that must all appear, e.g. 'additional insured' or 'CG 40 47'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rayoninsure-mcp/rayoninsure#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 77

## Common questions

### What is the Rayon Insurance MCP server?

Rayon Insurance is an MCP server listed in the public MCP registry as com.rayoninsure/mcp. Firm details, request forms, and contract review or quote requests with a robotics insurance broker. This page covers its hosted endpoint (https://rayoninsure.com/mcp).

### Is the Rayon Insurance MCP server safe to use?

Rayon Insurance 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 Rayon Insurance MCP server expose?

Rayon Insurance exposes 4 tools: get_firm_details, list_request_forms, submit_request, search_insurance_guides. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.

### Does the Rayon Insurance MCP server require authentication?

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

### Is the Rayon Insurance MCP server still maintained?

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

### What did VerifyMCP test on the Rayon Insurance MCP server?

VerifyMCP ran 13 checks on Rayon Insurance, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://rayoninsure.com/mcp
- Website: https://rayoninsure.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-rayoninsure-mcp/rayoninsure.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rayoninsure-mcp/rayoninsure/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-rayoninsure-mcp/rayoninsure.json
- HTML version of this page: https://verifymcp.io/servers/com-rayoninsure-mcp/rayoninsure
