Rayon Insurance
REMOTE · RAYONINSURE.COM
Firm details, request forms, and contract review or quote requests with a robotics insurance broker.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 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 Security83
- 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. 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. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4285 tokens (~102/item across 42 items; 4 tools + 38 resources), lean.Pass
- 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 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 77
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 21 Nov 2026 · Probed https://rayoninsure.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rayoninsure.com | CN=YR2,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 6f9e1becbe329982eb9f398f593c4b7cd04 |
| SANs: rayoninsure.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 secure
Validation of rayoninsure.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| rayoninsure.com. | DS published | 13071 | 13 | Verified |
| rayoninsure.com. | Verified address RRset verified with the apex keys |
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://rayoninsure.com/mcp | Verified | 200 | |
| http (plaintext) | http://rayoninsure.com/mcp | HTTPS enforced | 308 | https://rayoninsure.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_firm_details Get firm details ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_request_forms List request forms ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_insurance_guides Search insurance guides ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most guides to return. |
| query | string | yes | Words that must all appear, e.g. 'additional insured' or 'CG 40 47'. |
No output schema declared.
No examples provided.
submit_request Submit a request for the visitor ~369
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The company's legal name. Required for contract_review. |
| string | yes | The visitor's work email. The reply goes here. | |
| kind | string | yes | 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 | yes | The visitor's full name. |
| phone | string | – | Optional phone number. |
| visitor_confirmed | boolean | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · rayoninsure.com
claude mcp add --transport http com-rayoninsure-mcp 'https://rayoninsure.com/mcp'
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.