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.

The Comp Desk Builder

REMOTE · ADMIN.THECOMPDESK.COM

Build New York workers' comp calculators and skills in a private sandbox. Key by invitation.

+4 this week 64 Trust /100

Last scanned (13 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 7358 tokens (~222/item across 33 items; 33 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% 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 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 33 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 60

    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 · Probed https://admin.thecompdesk.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=admin.thecompdesk.com CN=YR1,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 RSA 2048 SHA256-RSA 6e48ca6d718f29ead5a5f906bafc974c93a
SANs: admin.thecompdesk.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of admin.thecompdesk.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thecompdesk.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; preload
content-security-policy default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https://ltibymvlytodkemdeeox.supabase.co; frame-src 'self' blob: https://ltibymvlytodkemdeeox.supabase.co; media-src 'self' blob: https://ltibymvlytodkemdeeox.supabase.co; connect-src 'self' https://ltibymvlytodkemdeeox.supabase.co wss://ltibymvlytodkemdeeox.supabase.co; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://admin.thecompdesk.com/mcp Verified 200
http (plaintext) http://admin.thecompdesk.com/mcp HTTPS enforced 308 https://admin.thecompdesk.com/mcp
MCP tools · 33 exposed · ~7,358 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
build_workspace_page ~161

Compose a WHOLE Pro Workspace page instead of one tile: several tiles (published slugs and/or inline declarative specs) over one shared global AWW and date of accident, each with its own inputs, in a saved layout. Returns the page object plus a self-contained HTML file that renders it with the live workspace renderer — the same no-eval whitelisted evaluator, so the numbers are the workspace's numbers, not this API's. Code tiles are never auto-run. Nothing publishes: create the calculators in your sandbox and submit_for_review as usual. Statutory max/min come from the date of accident via calc-core and cannot be supplied.

NameTypeReqDescription
globalobject––
namestring––
tilesarrayyes–

No output schema declared.

No examples provided.

calculate_apportionment ~219

A schedule loss of use apportioned across two to six established claims of one claimant: each case uses its own AWW and date of accident (its own max and min) and its APPORTIONED loss of use for each member, with any protracted healing period, prior payments and credits; returns each case's award, 15% fee rounded down to $5 and net, and the totals. Cases are numbered; no names. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
casesarrayyes–

No output schema declared.

No examples provided.

calculate_aww ~319

The average weekly wage from earnings in the year before the accident: earnings_method "steady" (WCL §14(1)–(2): earnings ÷ days worked × 200/260/300 for a 4-/5-/6-day week, 365 for 7) or "irregular" for new, seasonal or irregular work (§14(3)–(4): earnings ÷ weeks worked). With a date of accident it also gives the weekly rate. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
date_of_accidentstring–Optional: adds the weekly rate.
days_per_weekinteger–steady: days normally worked each week (1–4 use the 200 multiplier).
days_workednumber–steady: days actually worked in the period.
earnings_methodstringyes–
total_earningsnumberyesTotal gross earnings in the period, in dollars.
weeks_workednumber–irregular: weeks actually worked.

No output schema declared.

No examples provided.

calculate_aww_with_adjustments ~375

The average weekly wage the way the Pro Workspace's global AWW works it out: earnings_method "steady" (earnings ÷ days worked × the 200/260/300/365 multiplier for a 4-/5-/6-/7-day week ÷ 52) or "irregular" (earnings ÷ weeks worked), plus weekly tips, the weekly value of board, and a concurrent employer's weekly wage. With a date of accident it adds the two-thirds weekly rate within the max and min. For a 1–3 day week use calculate_aww. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
concurrent_weekly_wagenumber–Optional: weekly wage from a concurrent employer, in dollars.
date_of_accidentstring–Optional: adds the weekly rate. YYYY-MM-DD.
days_per_weekinteger–steady: days normally worked each week.
days_workednumber–steady: days actually worked in the period.
earnings_methodstringyes–
total_earningsnumberyesGross earnings in the period, in dollars.
weekly_boardnumber–Optional: weekly value of board/lodging, in dollars.
weekly_tipsnumber–Optional: weekly tips, in dollars.
weeks_workednumber–irregular: weeks actually worked.

No output schema declared.

No examples provided.

calculate_benefit_weeks ~216

Weeks between dates the way The Comp Desk's CCP / Award calculator counts them: both end dates count; a period that starts the day the previous one ended counts that day once; a period held in abeyance counts no weeks; weeks rounded down to none / tenth / whole. Returns per period the inclusive days, exact and rounded weeks, whether the shared boundary day was dropped, and the next day after the end. Dates only, no money. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
periodsarrayyes–
weeks_roundingstring–Optional; default none.

No output schema declared.

No examples provided.

calculate_burns_lien ~327

The carrier's equitable share of litigation costs on its workers' compensation lien when a third-party action recovers (WCL §29; Kelly; Burns): gross lien (indemnity + medical), the cost-share rate (attorney fee + disbursements ÷ gross recovery), the carrier's share and the net to the plaintiff. For a motor-vehicle case, give the no-fault threshold that comes off the lien first. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
attorney_feenumberyesThird-party attorney fee, in dollars.
disbursementsnumberyesLitigation disbursements, in dollars.
gross_recoverynumberyesGross third-party recovery, in dollars.
indemnity_liennumberyesIndemnity paid (lien), in dollars.
medical_liennumberyesMedical paid (lien), in dollars.
motor_vehicle_thresholdnumber–Optional, motor-vehicle cases: the amount that comes off the lien first, in dollars.

No output schema declared.

No examples provided.

calculate_ccp_award ~456

What is owed for one or more benefit periods (types TT total, TP partial with a disability %, RE reduced earnings with weekly earnings), the way The Comp Desk's CCP/Award calculator works it out: weeks from the dates (both ends count; a period starting the day the last ended counts it once; weeks rounded down to the tenth by default), each period's rate within the max and min, and the total award. With prior_payments (0 if none) it adds the claimant's money, the 15% fee exact to the cent, the OC-400.1 amount rounded down to $5 and the net; an employer reimbursement out of the whole award is split as on SLU. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
awwnumberyesAverage weekly wage before the injury, in dollars (gross).
date_of_accidentstringyesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
employer_reimbursementobject–Optional employer reimbursement (REIMB ER) out of the award: { "amount": dollars } or { "amount_unknown": true } when it is still TBD. Needs prior_payments (0 if none).
periodsarrayyes–
prior_counsel_feesarray–Optional. Dollar amount of the fee apportioned to each prior counsel (one or two). The current attorney gets the rest of the fee.
prior_paymentsnumber–Optional: dollars already paid on these periods (0 if none). Adds the fee and net.
weeks_roundingstring–Optional; default tenth.

No output schema declared.

No examples provided.

calculate_ccp_award_detailed ~460

The full Pro Workspace CCP / Award engine: periods of type TT (total), RE (reduced earnings, with current weekly earnings), TR / TP (a disability percentage of two-thirds of the wage, or a typed weekly rate), NCLT / NME ($0) and HIA (held in abeyance, no weeks); weeks counted with both ends, the shared boundary day once, rounded down to none / tenth / whole (default tenth); each rate within the max and min for the date of accident (RE capped, never raised); an amending period paid at its rate less a prior percentage or prior weekly rate; already-paid periods kept in the award but out of the money moving and fee; employer reimbursements per period with scope "period", "all" or a "specific" date range (or amount unknown); the CCP fee (the weekly CCP amount ÷ 3); prior payments; and the prior-counsel split. Returns every period, the award, the exact fee, the OC-400.1 amount rounded down to $5 and both nets. calculate_ccp_award is the simpler TT/TP/RE version. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
awwnumberyesAverage weekly wage, in dollars.
ccp_weekly_amountnumber–Optional: the weekly CCP amount; its fee is the amount ÷ 3.
date_of_accidentstringyesDate of accident. YYYY-MM-DD.
periodsarrayyes–
prior_counsel_feesarray–Optional: each prior counsel's dollar share of the fee.
prior_paymentsnumber–Optional: dollars already paid on these periods.
weeks_roundingstring–Optional; default tenth.

No output schema declared.

No examples provided.

calculate_fee_split ~243

Divides an attorney fee between the current attorney and one or two prior counsel the way every Comp Desk tile does: each prior counsel gets the dollar amount given, the current attorney the rest, worked in whole cents; prior amounts above the fee are flagged as over-allocated (nothing can be requested). Also gives the OC-400.1 amount: the current attorney's share rounded down to the nearest $5. The fee the Board approves can differ. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
prior_counsel_feesarrayyesDollar amount of the fee apportioned to each prior counsel (one or two).
total_feenumberyesThe total attorney fee, in dollars (for example the fee a calculator returned).

No output schema declared.

No examples provided.

calculate_lwec_award ~319

A permanent partial disability (non-schedule) award from a loss of wage-earning capacity percentage: the weekly rate (the bounded two-thirds rate × the LWEC %, kept within the max and min), the number of weeks for that LWEC bracket (§15(3)(w): 225 to 525 weeks depending on the bracket), the award, and, with the weeks of temporary benefits already paid, the credit for weeks beyond 130. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
awwnumberyesAverage weekly wage before the injury, in dollars (gross).
date_of_accidentstringyesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
lwec_percentnumberyesLoss of wage-earning capacity, 0–100 (50 means 50%).
prior_temporary_weeksnumber–Optional: weeks of temporary benefits already paid (for the 130-week credit).

No output schema declared.

No examples provided.

calculate_section_32_split ~267

How a Section 32 settlement divides: any Medicare set-aside comes off first, the attorney fee is 15% of the rest rounded down to $5, and the remainder is the claimant's net. Optional prior-counsel fee split (the OC-400.1 requests only the current attorney's share). The fee the Judge approves can differ. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
msa_amountnumber–Optional: the Medicare set-aside, in dollars.
prior_counsel_feesarray–Optional. Dollar amount of the fee apportioned to each prior counsel (one or two). The current attorney gets the rest of the fee.
settlement_amountnumberyesThe gross settlement, in dollars.

No output schema declared.

No examples provided.

calculate_slu_award ~521

A schedule loss of use award for one or more scheduled members: weeks on the schedule × loss of use % × the weekly rate for the date of accident, plus any protracted healing period credit (weeks at temporary total beyond the longest healing period, §15(4-a)). With prior_payments (0 if none) it adds the money moving, the 15% attorney fee rounded down to $5 (the OC-400.1 amount) and the net. With an employer reimbursement it splits the money and the fees between claimant and employer, exact to the cent; the fee on the reimbursement comes from the claimant's money when it is enough. Optional prior-counsel fee split. No 130-week credit on SLU. New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
awwnumberyesAverage weekly wage before the injury, in dollars (gross).
body_partsarrayyesEach scheduled member and its schedule loss of use percentage. Members: arm, hand, leg, foot, thumb, index/middle/ring/pinky finger, great toe, other toe, eye, one ear, both ears.
date_of_accidentstringyesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
employer_reimbursementobject–Optional employer reimbursement (REIMB ER) out of the award: { "amount": dollars } or { "amount_unknown": true } when it is still TBD. Needs prior_payments (0 if none).
prior_counsel_feesarray–Optional. Dollar amount of the fee apportioned to each prior counsel (one or two). The current attorney gets the rest of the fee.
prior_paymentsnumber–Optional: dollars of this award already paid (0 if none). Adds the fee and net.
weeks_at_temporary_totalnumber–Optional: weeks paid at temporary total, for the protracted healing period credit.

No output schema declared.

No examples provided.

calculate_slu_joint_replacement ~494

The schedule loss of use percentage for a shoulder, hip or knee replacement on its own scoring track (2018 NY Impairment Guidelines Tables 5.5 / 6.5 / 7.5, as the app's engine encodes them): the base, plus the value that most closely matches the deficit in each column (range of motion, position, atrophy, chronic complications), up to the table maximum. A failed replacement is reported as not schedulable. Shoulder takes flexion/abduction; hip takes flexion, leg-length discrepancy, mal-rotation, hip_fracture; knee takes flexion, extension contracture, malalignment, ML laxity, AP motion, leg length. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
abduction_degreesnumber–Shoulder: abduction, degrees.
ap_motion_mmnumber–Knee: anterior-posterior motion, millimetres.
atrophy_inchesnumber–Atrophy, inches (mid-arm for the shoulder, mid-thigh for hip/knee).
chronic_complicationsboolean––
extension_contracture_degreesnumber–Knee: extension contracture (flexion deformity), degrees.
failedboolean–The replacement failed (not schedulable).
flexion_degreesnumber–Flexion, degrees.
hip_fractureboolean–Hip: the replacement followed a fracture.
jointstringyes–
leg_length_discrepancy_inchesnumber–Hip or knee: leg-length discrepancy, inches.
mal_rotation_degreesnumber–Hip: mal-rotation, degrees.
malalignment_degreesnumber–Knee: malalignment, degrees.
ml_laxity_degreesnumber–Knee: medial-lateral laxity, degrees.
months_post_opnumber–Months since the replacement (the engine warns under its minimum).

No output schema declared.

No examples provided.

calculate_slu_percent_from_rom ~508

A schedule loss of use percentage range from measured range of motion, scored by the app's SLU range-of-motion engine (2018 NY Impairment Guidelines): each joint's deficit by severity band with proportional adjustment, the paired-motion rule (both_motions), the ankylosis cap for the body part, an optional special consideration (added or stand-alone, as the engine marks it), an optional contralateral baseline, and the shoulder muscle-atrophy finding. Joints per body part: Thumb IP/MCP/CMC (CMC is the opposition grade 1–3), Finger DIP/PIP/MCP, Wrist Palmar Flex/Dorsi Flex/Pron/Sup, Elbow Extension/Flexion, Shoulder Forward Flexion/Abduction/Int Rotation/Ext Rotation/Adduction/Post Extension, Hip Abduction/Adduction/Int Rotation/Ext Rotation/Flexion/Post Extension, Knee Flexion/Extension, Ankle/Foot Plantar Flex/Dorsi Flex/Inversion/Eversion, Great Toe IP/MTP Flex/MTP Ext, Smaller Toes DIP/PIP/MTP. Returns a percentage, not an award: pass the percentage to calculate_slu_award. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
body_partstringyes–
both_motionsarray–Optional: joints whose paired motion (extension, supination) is also deficient, so the higher figure applies.
contralateralobject–Optional: joint name → the uninjured side's degrees, used as the baseline.
measurementsobjectyesJoint name → measured degrees (Thumb CMC: opposition grade 1, 2 or 3). Joint names exactly as listed in the description.
shoulder_muscle_atrophyboolean–Optional, shoulder: a muscle-atrophy finding (gates the marked-rotation add).
special_considerationstring–Optional: a special consideration label exactly as the engine lists it for this body part (an invalid label returns the allowed list).

No output schema declared.

No examples provided.

calculate_weekly_rate ~327

A weekly benefit rate under the NY Workers' Compensation Law: kind "total" (temporary total: two-thirds of the AWW within the max and min for the date of accident; a wage below the minimum is paid in full), "partial" (temporary partial at a degree of disability, with the same bounds) or "reduced_earnings" (two-thirds of the wage loss, capped at the max, never raised to the min). New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
awwnumberyesAverage weekly wage before the injury, in dollars (gross).
current_weekly_earningsnumber–kind "reduced_earnings": gross weekly earnings now, in dollars.
date_of_accidentstringyesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
disability_percentnumber–kind "partial": degree of partial disability, 0–100 (50 means 50%).
kindstringyes–

No output schema declared.

No examples provided.

create_calculator ~69

Create a draft calculator in your sandbox (declarative spec or reviewed code tile).

NameTypeReqDescription
authoringstring––
codestring––
namestringyes–
slugstringyes–
specobject––
tierstring––

No output schema declared.

No examples provided.

create_skill ~131

Create a draft skill (SKILL.md bundle) in your sandbox. Skills must be self-sufficient: they cannot assume the attorney has a case-management system. A skill that needs external data (e.g. a claimant's wages) must drive the browser Claude is connected to — open the source like the WCB eCase portal, have the user log in, and fetch the document (e.g. the C-240) itself — or read the attorney's local files, or ask the user.

NameTypeReqDescription
namestringyes–
skill_mdstring––
slugstringyes–

No output schema declared.

No examples provided.

fork_calculator ~73

Copy an approved published calculator into your sandbox as a new draft to improve. Give the slug (or id) of the published calculator; optionally new_name / new_slug.

NameTypeReqDescription
idstring––
new_namestring––
new_slugstring––
slugstring––

No output schema declared.

No examples provided.

generate_fee_app ~287

Fill an OC-400.1 (Application for Fee by Claimant's Attorney) from computed award numbers and return it as an UNSIGNED PDF, through the same field map the Pro Workspace fills. It will NOT accept a signature and will NOT fill any attorney-identity field (Representative ID, firm, address, phone) — those are completed in the workspace by the attorney whose fee it is. It reads nothing from the database and does no fee math: pass feeRequestedDollar, or pass feeRequested and it is floored to the nearest $5 by the same rule the workspace uses. Owner-restricted. The result is a DRAFT, not a filing: check every figure against the tile it came from.

NameTypeReqDescription
claimantNamestring––
currentRolestring––
dateRetainedstring––
dateSubmittedstring––
deathBenefitsboolean––
feeEquationstring––
feeReasonsarray––
feeRequestednumber––
feeRequestedDollarstring––
include_pdfboolean––
otherFeesstring––
otherReasonCheckedboolean––
otherReasonTextstring––
priorRetainedstring––
servedNoticestring––
wcbNumberstring––

No output schema declared.

No examples provided.

get_calculator_template ~21

Return a starter declarative calculator spec to fill in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_formula ~145

The real NYS WC formula catalog behind the Comp Desk calculators: algebraic form, symbol table (what every symbol means), plain-language explanation, statutory/case citation, and a per-entry verified flag. Served from the SAME module the Pro Workspace shows, so the API and the app cannot disagree. Filter by id, by group (aww, rate, slu, lwec, perm, settle, fee), or by a free-text term; omit everything for the whole catalog. An entry with verified:false has NOT been through legal review — never present its citation as settled law.

NameTypeReqDescription
groupstring––
idstring––
qstring––

No output schema declared.

No examples provided.

get_max_min_rate ~215

The New York maximum and minimum weekly workers' compensation benefit for a date of accident (the rate year runs July 1 to June 30; the maximum is fixed by the date of accident, never by today's date). Use for "what is the max rate for a 2025 injury". New York State only. Computes with The Comp Desk calc-core (the engine behind the app, the website calculators and the Pro Workspace); it never estimates. If an input is missing it returns status "missing" with every input still needed and calculates nothing. Returns the figures, the rate year used, the formulas with their citations (each flagged with whether it has been attorney-reviewed), and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
date_of_accidentstringyesDate of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.

No output schema declared.

No examples provided.

get_notice_deadline ~167

The date written notice of the injury to the employer is due under the NY Workers' Compensation Law, counted from the date of accident, or from the date of disablement for an occupational condition that built up over time, with the days left from today in New York and the statute it comes from. New York State only; not a substitute for checking the facts. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
date_of_accidentstring–Date of accident (injury), YYYY-MM-DD. Only a full date the user gave; never a guessed one.
date_of_disablementstring–For an occupational condition: date of disablement, YYYY-MM-DD.

No output schema declared.

No examples provided.

get_reference ~87

The existing Comp Desk calculators (SLU, LWEC, CCP, AWW/concurrent employment, Burns, etc.): the calc-core function and statute behind each, the canonical source URL, and the ids of the formula-catalog entries that document each one. Start here, then call get_formula for the algebra. Use this to build on or improve an existing calculation instead of starting from scratch.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_review_status ~44

Check the status (submitted/changes_requested/approved/rejected/published) of your submissions.

NameTypeReqDescription
ref_idstring––
submission_idstring––

No output schema declared.

No examples provided.

list_published ~31

List the calculators already approved and published into the Pro Workspace, so you can fork one as a starting point.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sandbox ~25

List your sandbox: calculators, skills, and recent submissions with their review status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_calculator ~82

Generate a self-contained HTML file that renders this calculator as a real tile (same look as the live workspace). Save the returned html and open it in your browser to test before submitting.

NameTypeReqDescription
authoringstring––
codestring––
namestring––
slugstring––
specobject––

No output schema declared.

No examples provided.

pull_skill_scaffold ~48

Return a valid, self-sufficient SKILL.md scaffold (autonomy: standalone + browser/local-files/user-input data sources + a no-backend fallback section) to start a new skill.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rank_radiculopathy ~463

The cervical or lumbar radiculopathy severity ranking, scored the way the Pro Workspace Radiculopathy tile scores it, from the 2012 NYS Impairment Guidelines tables as calc-core carries them: imaging 16, EMG 6, muscle weakness by grade (0–1: 20, 2: 18, 3: 6, 4–5: 0) plus atrophy 6 under the root's weakness cap, sensory (compromised 4, anesthesia 6) under the root's sensory cap, reflex (diminished 4, absent 6), tension signs 4; the letter from Table S11.7. Give the findings (unlisted findings count as normal / no), or instead total_points to rank a total already scored. A total with no row on Table S11.7 (1–3 points, or above the top row) is refused with the reason, never given a letter. Cervical roots C5–T1, lumbar L3–S1. New York State only. Computes with The Comp Desk calc-core, the same engine as the app and the Pro Workspace; it never estimates. A missing input returns status "missing" and nothing is calculated. Returns the figures, the steps with the rule and engine function behind each, and the not-legal-advice notice. Needs your builder key. Same engine the Pro Workspace tiles call through CD.Calc, so a figure here matches the app to the cent.

NameTypeReqDescription
emgboolean–EMG fibrillations / positive sharp waves in 2+ muscles of the root.
imagingboolean–Imaging shows nerve-root displacement or encroachment that correlates.
muscle_atrophyboolean––
muscle_weakness_gradeinteger–Motor grade 0–5; default 5 (normal).
nerve_rootstring––
reflexstring––
regionstringyes–
sensorystring––
tension_signsboolean–Spurling's, straight leg raise or femoral stretch positive.
total_pointsnumber–Instead of the findings: a total already scored, to rank.

No output schema declared.

No examples provided.

submit_for_review ~83

Submit a sandbox calculator or skill to the owner for review. Nothing publishes without approval. Skills are gated by the Self-Sufficiency Contract — a backend-dependent skill is rejected at submit AND at approval; run validate_build first and fix any self_sufficient failures.

NameTypeReqDescription
kindstringyes–
notesstring––
ref_idstringyes–

No output schema declared.

No examples provided.

update_calculator ~68

Update one of your draft calculators by id.

NameTypeReqDescription
authoringstring––
codestring––
idstringyes–
namestring––
slugstring––
specobject––
tierstring––

No output schema declared.

No examples provided.

validate_build ~107

Validate a calculator spec or a skill SKILL.md before submitting. For skills this also runs the Self-Sufficiency Contract: the skill must complete its task with NO case-management backend — declare "autonomy: standalone", name a no-backend data source (browser / local-files / user-input), and document the fallback in a heading. Returns errors/warnings + self_sufficient.

NameTypeReqDescription
kindstring––
skill_mdstring––
specobject––

No output schema declared.

No examples provided.

Install

How do I install the The Comp Desk Builder MCP server?

The Comp Desk Builder is a hosted endpoint at https://admin.thecompdesk.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 · admin.thecompdesk.com

# add to Claude Code
claude mcp add --transport http com-thecompdesk-builder 'https://admin.thecompdesk.com/mcp'
Common questions

What is the The Comp Desk Builder MCP server?

The Comp Desk Builder is an MCP server listed in the public MCP registry as com.thecompdesk/builder. Build New York workers' comp calculators and skills in a private sandbox. Key by invitation. This page covers its hosted endpoint (https://admin.thecompdesk.com/mcp).

Is the The Comp Desk Builder MCP server safe to use?

The Comp Desk Builder scores 64 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 The Comp Desk Builder MCP server expose?

The Comp Desk Builder exposes 33 tools: get_reference, get_formula, preview_calculator, build_workspace_page, generate_fee_app, and 28 more. Their descriptions and schemas cost roughly 7,358 tokens of context every time the server is loaded.

Does the The Comp Desk Builder MCP server require authentication?

No. We connected to The Comp Desk Builder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the The Comp Desk Builder MCP server still maintained?

The Comp Desk Builder 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 did VerifyMCP test on the The Comp Desk Builder MCP server?

VerifyMCP ran 12 checks on The Comp Desk Builder, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about The Comp Desk Builder: Authorization. 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.