NAIC AI model bulletin adoption by state, with citations. Insurance AI compliance data.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://agentweb.brelsfordsoftware.com/mcp3 tools · 285mslookup_jurisdictionLook up one US jurisdiction's insurance-AI regulatory posture: whether it adopted the NAIC model bulletin, runs its own framework, or has other AI-related insurance legislation, with citations, dates and status. Call this when asked what a specific state requires, whether a state adopted the NAIC A…Look up one US jurisdiction's insurance-AI regulatory posture: whether it adopted the NAIC model bulletin, runs its own framework, or has other AI-related insurance legislation, with citations, dates and status. Call this when asked what a specific state requires, whether a state adopted the NAIC A…
| Parameter | Type | Description |
|---|---|---|
| jurisdiction* | string | Two-letter code or full name, e.g. 'CO' or 'Colorado' |
list_jurisdictionsList 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.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.
| Parameter | Type | Description |
|---|---|---|
| posture | string | adopted_model_bulletin = adopted the NAIC bulletin; own_framework = runs its own insurance-specific AI framework (CA, CO, NY, TX); no_model_bulletin = has not… |
| 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 |
dataset_provenanceReturn 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.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.
No input schema was published for this tool.
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
NAIC AI model bulletin adoption by state, with citations. Insurance AI compliance data.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.