Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Delegance business insurance

NPM · @DELEGANCE/CLI

Business insurance quotes with no API key: GL, workers comp, BOP, cyber. Bind, COIs, policies.

Available components

0 this week 59 Trust /100

Last scanned (13 hours ago)

Scores higher than 29% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 16 of 85 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2096 tokens (~131/item across 16 items; 16 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% 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
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 44

    First indexed and scored.

Diagnostics

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 · Analysed npm/@delegance/cli@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 85 packages
Packages resolved 85
Stale 15
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~2,016 tokens

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 →

Tool Tokens
check_appetite ~170

Which instant-quote carriers will write this business, per coverage line. No API key. Files nothing.

NameTypeReqDescription
annual_revenuenumber––
coveragesarrayyesCoverage lines, e.g. ["general_liability", "workers_comp", "bop", "property", "cyber", "professional_liability", "commercial_auto", "umbrella", "management_liability"]. management_liability quotes D&…
descriptionstring–One sentence on what the business does
naics_codestring–NAICS code, when known
statestringyesTwo-letter state code, e.g. "TX"

No output schema declared.

No examples provided.

delegance_agent_guide ~35

Read first. How to quote business insurance with these tools: no API key for quotes, what to gather, limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate_coi ~53

Issue a COI for policies on the account to a certificate holder. Servicing: needs an API key.

NameTypeReqDescription
holderobjectyes–
policy_idsarrayyes–
typestring––

No output schema declared.

No examples provided.

get_api_key ~37

Binding needs a verified email and servicing (COIs, policies, claims) needs an API key. Returns the one command your user runs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

indicative_quote ~171

Appetite plus an indicative premium range from comparable priced quotes. Not an offer, never bindable. No API key.

NameTypeReqDescription
annual_revenuenumber––
coveragesarrayyesCoverage lines, e.g. ["general_liability", "workers_comp", "bop", "property", "cyber", "professional_liability", "commercial_auto", "umbrella", "management_liability"]. management_liability quotes D&…
descriptionstring–One sentence on what the business does
naics_codestring–NAICS code, when known
statestringyesTwo-letter state code, e.g. "TX"

No output schema declared.

No examples provided.

licensing_approve_fee ~183

Raise the fee cap of a renewal paused at needs_input because the NIPR fee is above its cap; the renewal then resumes. Only call this after the user explicitly approves the new cap in this conversation. approved_by_name and approved_by_email must name the person who approved it; ask them, never invent the approver. Never send SSNs, FEINs or other tax ids, dates of birth, passwords (NIPR or any other), card or bank numbers: the API refuses them, and you must not ask the user for them. Servicing: needs an API key.

NameTypeReqDescription
approved_by_emailstringyesTheir email
approved_by_namestringyesWho approved the new cap
fee_cap_centsintegeryesThe new most authorized for this renewal, in cents
renewal_idstringyes–

No output schema declared.

No examples provided.

licensing_check_readiness ~96

What still blocks a licensee from a renewal: each blocker names the field, a code and what to do. Never send SSNs, FEINs or other tax ids, dates of birth, passwords (NIPR or any other), card or bank numbers: the API refuses them, and you must not ask the user for them. Servicing: needs an API key.

NameTypeReqDescription
licensee_idstringyes–

No output schema declared.

No examples provided.

licensing_create_licensee ~367

Register one insurance producer (individual or business) for NIPR license renewals. Only licensee_type and npn are required; licensing_check_readiness says what is still missing. Never send SSNs, FEINs or other tax ids, dates of birth, passwords (NIPR or any other), card or bank numbers: the API refuses them, and you must not ask the user for them. Sandbox (the default) files nothing. Servicing: needs an API key with the licensing scopes.

NameTypeReqDescription
attestationobject–The licensee's background answers: { questionSetVersion, answers: { <slug>: { answer: "yes"|"no", detail? } } }. Send with attestation_signed.
attestation_signedobject–{ signerName, signerEmail, relationship: "self"|"delegate", signedAt (ISO), delegationStatement? }
business_namestring––
consentobject–{ signerName, signerEmail, acceptedAt (ISO), statementVersion: "2026-11-05.v1" }
contact_emailstring––
default_fee_cap_centsinteger––
external_refstring–The caller's own id for this licensee
first_namestring––
last_namestring––
license_linesarray–e.g. property, casualty, life, accident_health
licensee_typestringyes–
modestring–sandbox (default) files and charges nothing
npnstringyesNational Producer Number, 1 to 10 digits
renew_statesarray–Two-letter USPS codes
resident_statestring–Two-letter USPS code

No output schema declared.

No examples provided.

licensing_get_renewal ~88

Status, step, fee and any needs_input or failure of one renewal. Never send SSNs, FEINs or other tax ids, dates of birth, passwords (NIPR or any other), card or bank numbers: the API refuses them, and you must not ask the user for them. Servicing: needs an API key.

NameTypeReqDescription
renewal_idstringyes–

No output schema declared.

No examples provided.

licensing_list_receipts ~112

Receipts of completed renewals: order number, fee, states and the receipt PDF route. Never send SSNs, FEINs or other tax ids, dates of birth, passwords (NIPR or any other), card or bank numbers: the API refuses them, and you must not ask the user for them. Servicing: needs an API key.

NameTypeReqDescription
cursorstring––
limitinteger––
modestring–sandbox (default) files and charges nothing

No output schema declared.

No examples provided.

licensing_queue_renewals ~235

Queue NIPR renewals for up to 500 ready licensees as one batch. authorized_by_name and authorized_by_email must name the person who approved paying state fees up to fee_cap_cents per renewal; ask them first, never invent them. A renewal whose fee is above the cap pauses at needs_input. Never send SSNs, FEINs or other tax ids, dates of birth, passwords (NIPR or any other), card or bank numbers: the API refuses them, and you must not ask the user for them. Sandbox (the default) files and charges nothing. Servicing: needs an API key.

NameTypeReqDescription
authorized_by_emailstringyes–
authorized_by_namestringyes–
fee_cap_centsintegeryesMost authorized per renewal, in cents
licensee_idsarrayyes–
modestring–sandbox (default) files and charges nothing
report_emailsarray–Owner or admin emails for the batch report; all of them when absent
scenariostring–Sandbox only: the outcome to simulate

No output schema declared.

No examples provided.

list_policies ~30

Active policies on the account. Servicing: needs an API key.

NameTypeReqDescription
statusstring––

No output schema declared.

No examples provided.

quote_needs ~165

The open questions for a quote and the documents that answer them (dec pages, loss runs, SOV, payroll or WC audit, vehicle schedule, contracts with insurance requirements), with likely file names, keywords and what to extract. Ask your user before you read any private file. No API key.

NameTypeReqDescription
coveragesarrayyesCoverage lines, e.g. ["general_liability", "workers_comp", "bop", "property", "cyber", "professional_liability", "commercial_auto", "umbrella", "management_liability"]. management_liability quotes D&…
heldarray–Fields you already have

No output schema declared.

No examples provided.

quote_status ~44

Premiums and carrier answers for a quote. Quotes show bindable:false until the user signs up (delegance signup). No API key.

NameTypeReqDescription
quote_idstringyes–

No output schema declared.

No examples provided.

start_quote ~179

Start a real instant quote with carriers (CoverForce markets). Returns quoteId and the carriers' questions, prefilled from agent_answers. Files nothing until submit_quote_answers. No API key.

NameTypeReqDescription
agent_answersarray–Facts you found with your user's permission. Labelled agent-supplied and cited on the quote. Never tax ids, SSNs, dates of birth or license numbers.
businessobjectyes–
coveragesarrayyesCoverage lines, e.g. ["general_liability", "workers_comp", "bop", "property", "cyber", "professional_liability", "commercial_auto", "umbrella", "management_liability"]. management_liability quotes D&…

No output schema declared.

No examples provided.

submit_quote_answers ~51

File the answers to the carriers' questions for a quote from start_quote. Real carrier filing. No API key.

NameTypeReqDescription
answersobjectyesquestion id -> value
quote_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Delegance business insurance MCP server?

Delegance business insurance runs locally as an npm package, launched with npx -y @delegance/cli mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @delegance/cli

# add to Claude Code
claude mcp add delegance-brokerage-delegance -- npx -y @delegance/cli mcp
Common questions

What is the Delegance business insurance MCP server?

Delegance business insurance is an MCP server listed in the public MCP registry as io.github.Delegance-Brokerage/delegance. Business insurance quotes with no API key: GL, workers comp, BOP, cyber. Bind, COIs, policies. This page covers its npm package (@delegance/cli).

Is the Delegance business insurance MCP server safe to use?

Delegance business insurance scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Delegance business insurance MCP server expose?

Delegance business insurance exposes 16 tools: delegance_agent_guide, check_appetite, quote_needs, indicative_quote, start_quote, and 11 more. Their descriptions and schemas cost roughly 2,016 tokens of context every time the server is loaded.

Is the Delegance business insurance MCP server still maintained?

Delegance business 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 licence is the Delegance business insurance MCP server under?

Delegance business insurance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Delegance business insurance MCP server?

VerifyMCP ran 14 checks on Delegance business insurance, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Delegance business insurance: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.