onehq-comissions-calculator
Description
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, Dire
What our measurements say
onehq-comissions-calculator is a remote MCP server published at onehq.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 477 ms, placing it among the faster endpoints. It offers a narrow, focused set of 5 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names clearly indicate their primary function (e.g., 'calculate_commission', 'build_hierarchy')
- Descriptions explain both purpose and specific use cases (e.g., 'validate against carrier rules')
- Clear differentiation between hierarchy-building and validation tools
Weaknesses
- No explicit parameter schema details provided for tool inputs/outputs
- Some tools (e.g., 'onehq_info') have less actionable descriptions compared to others
- Error handling documentation is only explicitly mentioned in 'validate_hierarchy'
calculate_commission— No explicit parameter schema details providedbuild_hierarchy— No explicit parameter schema details providedvalidate_hierarchy— No explicit parameter schema details providedget_carrier_info— No explicit parameter schema details providedonehq_info— Description lacks actionable use case specifics
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — Era changed from 'auth-gated' to 'legacy' · Transition to legacy era may affect compliance checks
- 2026-09-11T05:44:28.819Z — Compliance score changed from null to 100 · Full compliance achieved in legacy era
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 367ms → warm 227ms (penalty 140ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.0.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/dante-r-g36u-onehq-comissions-calculator)<a href="https://mcpmetrics.io/servers/dante-r-g36u-onehq-comissions-calculator"><img src="https://mcpmetrics.io/badge/dante-r-g36u/onehq-comissions-calculator/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see