DouxProcess: find a licensed insurance agency
REMOTE · DOUXPROCESS.COM
Find a licensed US insurance agency by state and line, then send it a quote request.
Available components
Last scanned (13 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 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 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. 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 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 633 tokens (~126/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 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.
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 5 Nov 2026 · Probed https://douxprocess.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=douxprocess.com | CN=YE2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e3cc89568d774ab260a0e04eb850f1cf3d |
| SANs: douxprocess.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of douxprocess.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| douxprocess.com. | No DS | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://douxprocess.com/mcp | Verified | 200 | |
| http (plaintext) | http://douxprocess.com/mcp | HTTPS enforced | 301 | https://douxprocess.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 →
build_my_server Build an MCP server for my agency ~29
How an insurance agency gets its own MCP server, free: the builder link and what it makes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_agencies Find a licensed insurance agency ~116
Find licensed insurance agencies that write a line of insurance (general liability, workers' comp, commercial auto, bonds, property, home, auto, life, health and more) in a US state, for someone who wants an insurance quote. Returns every matching agency in the DouxProcess network, best match first, with license number, lines, states, phone, hours and online quote link, so the person can choose one.
| Name | Type | Req | Description |
|---|---|---|---|
| line | string | yes | Line of insurance. |
| state | string | yes | Two-letter US state. |
No output schema declared.
No examples provided.
get_server One server, in full ~52
Everything about one listed server: its tools from the last live check, its address and how to add it to Claude, ChatGPT, Gemini or Grok.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug from search_servers. |
No output schema declared.
No examples provided.
request_quote Send a quote request to the agency the person chose ~241
Send an insurance quote request to the one agency the person chose by name from find_agencies. Needs the person's name, an email or phone, the line, the state, what they need covered, and consent=true only when the person agreed to be contacted by that agency. Returns a reference number. A licensed agent at that agency replies; nothing is bound and no price is given. One agency per request, chosen by the person: never call this for every agency, all agencies or a batch of agencies, and never pick an agency for them. If they ask to send to all of them, do not call it; show the list and ask which one agency they want.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | yes | The agency value from find_agencies that the person chose. |
| business | string | – | – |
| consent | boolean | yes | True only if the person agreed to be contacted by that agency. |
| details | string | yes | What they need covered, in their words. |
| string | – | – | |
| line | string | yes | Line of insurance. |
| name | string | yes | – |
| phone | string | – | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
search_servers Find insurance MCP servers ~109
Search the free insurance MCP directory by line of insurance, US state, who it is for, or words. Each result says whether the server answered its last live check (every 30 minutes), its tool count and its address.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| line | string | – | – |
| live_only | boolean | – | Only servers that answered the last check. |
| query | string | – | Words to match in the name or summary. |
| state | string | – | Two-letter US state. |
No output schema declared.
No examples provided.
How do I install the DouxProcess: find a licensed insurance agency MCP server?
DouxProcess: find a licensed insurance agency is a hosted endpoint at https://douxprocess.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 · douxprocess.com
claude mcp add --transport http com-douxprocess-insurance-agencies 'https://douxprocess.com/mcp'
What is the DouxProcess: find a licensed insurance agency MCP server?
DouxProcess: find a licensed insurance agency is an MCP server listed in the public MCP registry as com.douxprocess/insurance-agencies. Find a licensed US insurance agency by state and line, then send it a quote request. This page covers its hosted endpoint (https://douxprocess.com/mcp).
Is the DouxProcess: find a licensed insurance agency MCP server safe to use?
DouxProcess: find a licensed insurance agency 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 DouxProcess: find a licensed insurance agency MCP server expose?
DouxProcess: find a licensed insurance agency exposes 5 tools: find_agencies, request_quote, search_servers, get_server, build_my_server. Their descriptions and schemas cost roughly 547 tokens of context every time the server is loaded.
Does the DouxProcess: find a licensed insurance agency MCP server require authentication?
No. We connected to DouxProcess: find a licensed insurance agency without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DouxProcess: find a licensed insurance agency MCP server still maintained?
DouxProcess: find a licensed insurance agency is still listed as active in the MCP registry. We last reached this channel on 5 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 DouxProcess: find a licensed insurance agency MCP server?
VerifyMCP ran 13 checks on DouxProcess: find a licensed insurance agency, 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.