OneHQ Commission Calculator MCP is a MCP server that gives AI assistants direct access to insurance commission calculation and compliance tools. It lets you model distribution hierarchies, calculate exact earnings per agent tier, validate structures against real carrier rules, and look up benchmark contract ranges — all without leaving your AI workflow. The OneHQ Commission Calculator MCP exposes 5 tools: 1. calculate_commission — Computes exact earnings per agent given an annual premium and a hierarchy of contract percentages. Returns direct commissions and override spreads at every tier. Preferred input: annual_premium (number) + agents array with name and contract_pct per tier. Example output: IMO override $1,200 / BGA override $1,200 / Agent direct $10,800 / Total distributed $13,200. 2. build_hierarchy — Takes named tiers and returns a validated, sorted hierarchy ready to feed into calculate_commission. Also provides 4 pre-built templates: Standard BGA, BGA with MGA, Direct Agent, and Multi-Level. Preferred input: tiers array with name and contract_pct per level. Example output: sorted tier list with validation status and 4 template options. 3. validate_hierarchy — Checks a hierarchy against a specific carrier's allowed contract ranges before submission. Returns a pass/fail result with tier-by-tier errors and warnings. Preferred input: carrier name (e.g. "protective", "mutual-of-omaha") + hierarchy array with name and pct per tier. Example output: overall PASS/FAIL, per-tier range check results, and a warning count. 4. get_carrier_info — Returns typical contract percentage ranges per tier (Agent, MGA, BGA, IMO) and maximum hierarchy totals for 6 supported carriers. Call with no argument to list all available carriers. Preferred input: carrier name (optional). Omit to get the full carrier list. Example output: Agent range 85–100%, BGA range 105–120%, IMO range 115–130%, max hierarchy 145%. 5. onehq_info — Returns a structured overview of the OneHQ platform (ICM, CRM, DMS, Agent Portal, Data Visualization) with relevant links. Optionally filter by topic to narrow results. Preferred input: topic string (optional) — e.g. "commissions", "crm", "agent portal". Example output: matching module name, description, and documentation link.

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (2249 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	31/31 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 5 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (2249 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 95% of peers; This listing 88 · peer median 81
Latency: Faster than 14% of peers; This listing 766 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/dante-r-g36u/onehq-comissions-calculator/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/dante-r-g36u/onehq-comissions-calculator/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.onehq.com/

Listed at (smithery)

https://www.onehq.com/