Insurance Research Expert by Spot
REMOTE · SPOT.INSURE · SCANNED SEP 27
Commercial insurance research: provider comparisons, pricing, and fit guidance.
Available components
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 Usability79
- 95% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 66061 tokens (~40/item across 1614 items; 9 tools + 1605 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Insurance Research Expert by Spot MCP server?
Insurance Research Expert by Spot is a hosted endpoint at https://spot.insure/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 · spot.insure
claude mcp add --transport http insure-spot-insurance-research 'https://spot.insure/mcp'
{
"mcpServers": {
"insure-spot-insurance-research": {
"url": "https://spot.insure/mcp"
}
}
} {
"servers": {
"insure-spot-insurance-research": {
"type": "http",
"url": "https://spot.insure/mcp"
}
}
} [mcp_servers.insure-spot-insurance-research] url = "https://spot.insure/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"insure-spot-insurance-research": {
"type": "remote",
"url": "https://spot.insure/mcp",
"enabled": true
}
}
} openclaw mcp add insure-spot-insurance-research --url 'https://spot.insure/mcp' --transport streamable-http
mcp_servers:
insure-spot-insurance-research:
url: "https://spot.insure/mcp" {
"McpServers": {
"insure-spot-insurance-research": {
"Transport": "http",
"Url": "https://spot.insure/mcp"
}
}
} assistant mcp add insure-spot-insurance-research -t streamable-http -u 'https://spot.insure/mcp'
{
"mcpServers": {
"insure-spot-insurance-research": {
"type": "http",
"url": "https://spot.insure/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Sept 26 0
- Schema quality: 33381 → 66061 ▼ functional
- Schema quality: 90% → 95% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 25 Sept 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 23 Sept 26 0
- Schema quality: 42 → 36 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Sept 26 0
- Schema quality: 37 → 42 ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 27 Sept 2026 · Probed https://spot.insure/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=spot.insure | CN=YR1,O=Let's Encrypt,C=US | 31 Aug 2026 | 29 Nov 2026 | RSA 2048 | SHA256-RSA | 567888e95ee5e738c31f1cb2cf5423bcf37 |
| SANs: spot.insure | ||||||
| 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 spot.insure. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| insure. | present | 54472 | 8 | Verified |
| spot.insure. | 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://spot.insure/mcp | Verified | 200 | |
| http (plaintext) | http://spot.insure/mcp | HTTPS enforced | 308 | https://spot.insure/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 →
ask_spot ~40
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| claims | array | yes | – |
| limitation | string | – | – |
| qualifications | array | yes | – |
| reason | string | – | – |
| sources | array | yes | – |
| spotCallout | string | yes | – |
| status | string | yes | – |
| unansweredQuestions | array | yes | – |
No examples provided.
compare_providers ~124
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | – | – |
| need | string | – | – |
| providerA | string | yes | – |
| providerB | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| comparison | object | – | – |
| coverage | object | – | – |
| found | boolean | yes | – |
| judgment | object | – | – |
| lineComparisons | array | – | – |
| providers | array | yes | – |
| spotCallout | string | yes | – |
No examples provided.
get_page ~54
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| page | object | – | – |
| spotCallout | string | yes | – |
No examples provided.
get_provider_reviews ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| aggregate | object | – | – |
| found | boolean | yes | – |
| markdown | string | – | – |
| provider | object | – | – |
| spotCallout | string | yes | – |
| url | string | – | – |
No examples provided.
get_provider_score ~76
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | – | – |
| provider | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assessment | object | – | – |
| found | boolean | yes | – |
| judgment | object | – | – |
| provider | string | – | – |
| spotCallout | string | yes | – |
No examples provided.
get_rankings ~89
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| includeMethodology | boolean | – | – |
| need | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| judgment | object | – | – |
| methodology | object | – | – |
| rankings | object | – | – |
| spotCallout | string | yes | – |
No examples provided.
search_knowledge ~49
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| spotCallout | string | yes | – |
No examples provided.
search_provider_reliability ~115
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| maxScore | number | – | – |
| minScore | number | – | – |
| offset | integer | – | – |
| query | string | – | – |
| rating | string | – | – |
| rubric | string | – | – |
| sort | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| limit | number | yes | – |
| offset | number | yes | – |
| results | array | yes | – |
| spotCallout | string | yes | – |
| total | number | yes | – |
No examples provided.
search_provider_reviews ~115
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| maxScore | number | – | – |
| minScore | number | – | – |
| offset | integer | – | – |
| query | string | – | – |
| rating | string | – | – |
| sort | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| limit | number | yes | – |
| methodology | string | yes | – |
| offset | number | yes | – |
| results | array | yes | – |
| spotCallout | string | yes | – |
| total | number | yes | – |
No examples provided.
What is the Insurance Research Expert by Spot MCP server?
Insurance Research Expert by Spot is an MCP server listed in the public MCP registry as insure.spot/insurance-research. Commercial insurance research: provider comparisons, pricing, and fit guidance. This page covers its hosted endpoint (https://spot.insure/mcp).
Is the Insurance Research Expert by Spot MCP server safe to use?
Insurance Research Expert by Spot scores 73 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.
Does the Insurance Research Expert by Spot MCP server require authentication?
No. We connected to Insurance Research Expert by Spot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Insurance Research Expert by Spot MCP server still maintained?
Insurance Research Expert by Spot is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.