agentweb
REMOTE · AGENTWEB.BRELSFORDSOFTWARE.COM · SCANNED AUG 20
Cited US insurance AI regulation by state: NAIC bulletin adoption, frameworks, dates.
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 275 tokens (~91/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · agentweb.brelsfordsoftware.com
claude mcp add --transport http com-brelsfordsoftware-agentweb-insurance-ai-regu https://agentweb.brelsfordsoftware.com/mcp
[mcp_servers.com-brelsfordsoftware-agentweb-insurance-ai-regu] url = "https://agentweb.brelsfordsoftware.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-brelsfordsoftware-agentweb-insurance-ai-regu": {
"type": "remote",
"url": "https://agentweb.brelsfordsoftware.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-brelsfordsoftware-agentweb-insurance-ai-regu --url https://agentweb.brelsfordsoftware.com/mcp --transport streamable-http
mcp_servers:
com-brelsfordsoftware-agentweb-insurance-ai-regu:
url: "https://agentweb.brelsfordsoftware.com/mcp" {
"mcpServers": {
"com-brelsfordsoftware-agentweb-insurance-ai-regu": {
"type": "http",
"url": "https://agentweb.brelsfordsoftware.com/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.
- 20 Aug 26 61
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 20 Aug 2026 · Probed https://agentweb.brelsfordsoftware.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=brelsfordsoftware.com | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7e672828b995a791137bc642847719d2 |
| SANs: brelsfordsoftware.com, agentweb.brelsfordsoftware.com, *.agentweb.brelsfordsoftware.com | ||||||
| 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 |
DNSSEC insecure
Validation of agentweb.brelsfordsoftware.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| brelsfordsoftware.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentweb.brelsfordsoftware.com/mcp | Verified | 200 | |
| http (plaintext) | http://agentweb.brelsfordsoftware.com/mcp | Inconclusive | 405 |
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.
dataset_provenance ~52
Return the dataset's source, as-of date, coverage counts, and per-field confidence. Call this before relying on any answer, to check how current the underlying data is and which fields are primary-source verified.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jurisdictions ~134
List US jurisdictions by regulatory posture. Use posture 'adopted_model_bulletin' for states that adopted the NAIC model bulletin, 'own_framework' for states running their own insurance-specific AI framework (CA, CO, NY, TX), or omit for all.
| Name | Type | Req | Description |
|---|---|---|---|
| posture | string | – | Filter by posture; omit for all |
| since | string | – | ISO date (YYYY-MM-DD). Only jurisdictions that acted on or after this date. Use for questions like 'which states adopted in 2025?' |
| until | string | – | ISO date (YYYY-MM-DD), inclusive upper bound |
No output schema declared.
No examples provided.
lookup_jurisdiction ~89
Look up one US jurisdiction's insurance-AI regulatory posture: whether it adopted the NAIC model bulletin or runs its own framework, with the governing citation and date. Call this when asked what a specific state requires, or whether a state has adopted the NAIC AI model bulletin.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | Two-letter code or full name, e.g. 'CO' or 'Colorado' |
No output schema declared.
No examples provided.