MCP servers › com.thecompdesk › nys-workers-comp-hub
MCP server · registry snapshot 2026-11-14 · last tested 2026-11-14
nys-workers-comp-hub MCP server
Registry name com.thecompdesk/nys-workers-comp-hub
New York State Workers' Compensation Hub — the publisher's title
by thecompdesk.com · domain (the registry's namespace rule)repository owner on GitHub: jmays2294-creator (personal account)Source ↗Website ↗
New York workers' comp calculators, rates, forms, glossary, case law and a doctor finder. — the publisher's description
Summary
com.thecompdesk/nys-workers-comp-hub is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain thecompdesk.com. Its linked repository is github.com/jmays2294-creator/nys-workers-comp-hub; GitHub reports its owner as jmays2294-creator, a personal account. On 2026-11-14 ProtocolProbe connected to it in read-only mode and read its inventory: 32 tools, 0 resources and 0 prompts.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 32
- Last tested
- 2026-11-14
Tool list size
17,647 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (32 tools). Counted with Anthropic's token counter on 2026-11-14, from the tool list we read on 2026-11-14. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-14 (ltibymvlytodkemdeeox.supabase.co), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.0.0).
Observed fact
This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (add_workspace_cases). That is our reading of the names; we did not call it. Source: our connection, 2026-11-14.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-14
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-11-13 (registry, as of the 2026-11-14 snapshot)
- First listed version
- 2026-11-13 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-14
- Package and repository
- checked 2026-11-14
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-13, listed on 2026-11-14 with version 1.0.0 (published 2026-11-13).
Source: the official MCP Registry list on 2026-11-13 and on 2026-11-14.
What it is
What does this server offer?
Observed inventoryNone of its 32 tools are described as changing anything. For 32 the reading was uncertain, so no mark is shown.
- get_max_min_rate
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
date_of_accidentstringrequired“Date of accident (injury), YYYY-MM-DD.”
- calculate_weekly_rate
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 3 required
kindstringrequiredawwnumberrequired“Average weekly wage before the injury, in dollars (gross).”date_of_accidentstringrequired“Date of accident (injury), YYYY-MM-DD.”disability_percentnumber“kind "partial": degree of partial disability, 0–100 (50 means 50%).”current_weekly_earningsnumber“kind "reduced_earnings": gross weekly earnings now, in dollars.”
- calculate_aww
“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"…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 2 required
earnings_methodstringrequiredtotal_earningsnumberrequired“Total gross earnings in the period, in dollars.”days_workednumber“steady: days actually worked in the period.”days_per_weekinteger“steady: days normally worked each week (1–4 use the 200 multiplier).”weeks_workednumber“irregular: weeks actually worked.”date_of_accidentstring“Optional: adds the weekly rate.”
- calculate_slu_award
“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 t…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 3 required
awwnumberrequired“Average weekly wage before the injury, in dollars (gross).”date_of_accidentstringrequired“Date of accident (injury), YYYY-MM-DD.”body_partsarrayrequired“Each scheduled member and its schedule loss of use percentage.”weeks_at_temporary_totalnumber“Optional: weeks paid at temporary total, for the protracted healing period credit.”prior_paymentsnumber“Optional: dollars of this award already paid (0 if none).”employer_reimbursementobject“Optional employer reimbursement (REIMB ER) out of the award: { "amount": dollars } or { "amount_unknown": true } when it is still TBD.”prior_counsel_feesarray“Optional.”
- calculate_lwec_award
“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 numbe…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 3 required
awwnumberrequired“Average weekly wage before the injury, in dollars (gross).”date_of_accidentstringrequired“Date of accident (injury), YYYY-MM-DD.”lwec_percentnumberrequired“Loss of wage-earning capacity, 0–100 (50 means 50%).”prior_temporary_weeksnumber“Optional: weeks of temporary benefits already paid (for the 130-week credit).”
- calculate_ccp_award
“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: wee…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 3 required
awwnumberrequired“Average weekly wage before the injury, in dollars (gross).”date_of_accidentstringrequired“Date of accident (injury), YYYY-MM-DD.”periodsarrayrequiredprior_paymentsnumber“Optional: dollars already paid on these periods (0 if none).”employer_reimbursementobject“Optional employer reimbursement (REIMB ER) out of the award: { "amount": dollars } or { "amount_unknown": true } when it is still TBD.”weeks_roundingstring“Optional; default tenth.”prior_counsel_feesarray“Optional.”
- calculate_section_32_split
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
settlement_amountnumberrequired“The gross settlement, in dollars.”msa_amountnumber“Optional: the Medicare set-aside, in dollars.”prior_counsel_feesarray“Optional.”
- calculate_burns_lien
“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 (…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 5 required
gross_recoverynumberrequired“Gross third-party recovery, in dollars.”indemnity_liennumberrequired“Indemnity paid (lien), in dollars.”medical_liennumberrequired“Medical paid (lien), in dollars.”attorney_feenumberrequired“Third-party attorney fee, in dollars.”disbursementsnumberrequired“Litigation disbursements, in dollars.”motor_vehicle_thresholdnumber“Optional, motor-vehicle cases: the amount that comes off the lien first, in dollars.”
- calculate_apportionment
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
casesarrayrequired
- get_notice_deadline
“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 t…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
date_of_accidentstring“Date of accident (injury), YYYY-MM-DD.”date_of_disablementstring“For an occupational condition: date of disablement, YYYY-MM-DD.”
- lookup_formula
“The Comp Desk's catalog of New York workers' compensation formulas (AWW, rates and bounds, SLU, LWEC, Section 32, Burns, attorney fee): the formula, what each symbol means, a plain explanation, the s…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
idstring“A formula id, e.g.”querystring“Words to search for, e.g.”
- define_termon 21 other servers
“A New York workers' compensation term from The Comp Desk glossary (AWW, SLU, LWEC, PFME, IME, ANCR, Section 32, CCP, form numbers and more): its meaning, detail, related terms and the source it comes…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
termstringquerystring
Show 20 more tools
- get_explaineron 1 other server
“A reviewed, plain-language explainer of one New York workers' compensation topic (for example AWW, SLU, ANCR), written for injured workers and usable with clients: its sentences, the definition, rela…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
slugstring“e.g.”
- search_wc_knowledge
“Searches The Comp Desk's approved knowledge base of New York workers' compensation questions and answers (benefits, permanency, IMEs, Section 32, labor market attachment, Board procedure, forms), eac…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
querystringrequired“The question or topic, in plain words.”limitinteger
- search_case_lawon 8 other servers
“Searches The Comp Desk's approved library of New York workers' compensation decisions (Court of Appeals and Appellate Division), each pulled and KeyCited in Westlaw before approval: case name, citati…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
querystringrequired“The issue, e.g.”limitinteger
- lookup_wcb_form
“What a New York Workers' Compensation Board form is (for example C-3, C-4, C-4.3, RB-89, OC-400.1), from The Comp Desk's approved glossary and knowledge base, with the Board's link.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
formstringrequired“The form number, e.g.”
- find_providerson 14 other servers
“Searches The Comp Desk's directory of medical providers in New York City's five boroughs (public CMS NPI Registry listings) by borough or ZIP code, specialty, language and whether they accept new pat…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs
boroughstringzipstring“5-digit ZIP code.”specialtystringlanguagestring“e.g.”accepting_new_patientsbooleanlimitinteger
- list_skillson 58 other servers
“The workflow skills that come with the New York State Workers' Compensation Hub (preparing cases for the Pro Workspace, explaining a benefit to a client, checking a Section 32 split, finding a WCB-au…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_skillon 90 other servers
“The full text (SKILL.md) of one Hub skill, for people using the connector without the plugin.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
namestringrequired“A skill name from list_skills.”
- describe_case_schema
“The exact case format add_workspace_cases accepts: every field of every calculator tile, the body-part names, the CCP designations, what is refused and why (statutory rates and results are derived by…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- add_workspace_cases
“Signed-in Pro or Firm attorneys only.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
3 inputs, 3 required
formatstringrequiredversionintegerrequiredcasesarrayrequired
- get_import_statuson 3 other servers
“Signed-in Pro or Firm attorneys only.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
keysarray
- calculate_slu_percent_from_rom
“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 propo…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 2 required
body_partstringrequiredmeasurementsobjectrequired“Joint name → measured degrees (Thumb CMC: opposition grade 1, 2 or 3).”special_considerationstring“Optional: a special consideration label exactly as the engine lists it for this body part (an invalid label returns the allowed list).”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.”shoulder_muscle_atrophyboolean“Optional, shoulder: a muscle-atrophy finding (gates the marked-rotation add).”
- calculate_slu_joint_replacement
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
14 inputs, 1 required
jointstringrequiredflexion_degreesnumber“Flexion, degrees.”abduction_degreesnumber“Shoulder: abduction, degrees.”extension_contracture_degreesnumber“Knee: extension contracture (flexion deformity), degrees.”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.”ap_motion_mmnumber“Knee: anterior-posterior motion, millimetres.”atrophy_inchesnumber“Atrophy, inches (mid-arm for the shoulder, mid-thigh for hip/knee).”chronic_complicationsbooleanmonths_post_opnumber“Months since the replacement (the engine warns under its minimum).”hip_fractureboolean“Hip: the replacement followed a fracture.”failedboolean“The replacement failed (not schedulable).”
- calculate_benefit_weeks
“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 abeyan…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
periodsarrayrequiredweeks_roundingstring“Optional; default none.”
- calculate_fee_split
“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, wo…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
total_feenumberrequired“The total attorney fee, in dollars (for example the fee a calculator returned).”prior_counsel_feesarrayrequired“Dollar amount of the fee apportioned to each prior counsel (one or two).”
- calculate_aww_with_adjustments
“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 "irre…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs, 2 required
earnings_methodstringrequiredtotal_earningsnumberrequired“Gross earnings in the period, in dollars.”days_workednumber“steady: days actually worked in the period.”days_per_weekinteger“steady: days normally worked each week.”weeks_workednumber“irregular: weeks actually worked.”weekly_tipsnumber“Optional: weekly tips, in dollars.”weekly_boardnumber“Optional: weekly value of board/lodging, in dollars.”concurrent_weekly_wagenumber“Optional: weekly wage from a concurrent employer, in dollars.”date_of_accidentstring“Optional: adds the weekly rate.”
- rank_radiculopathy
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
10 inputs, 1 required
regionstringrequirednerve_rootstringimagingboolean“Imaging shows nerve-root displacement or encroachment that correlates.”emgboolean“EMG fibrillations / positive sharp waves in 2+ muscles of the root.”muscle_weakness_gradeinteger“Motor grade 0–5; default 5 (normal).”muscle_atrophybooleansensorystringreflexstringtension_signsboolean“Spurling's, straight leg raise or femoral stretch positive.”total_pointsnumber“Instead of the findings: a total already scored, to rank.”
- calculate_ccp_award_detailed
“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 week…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 3 required
awwnumberrequired“Average weekly wage, in dollars.”date_of_accidentstringrequired“Date of accident.”periodsarrayrequiredweeks_roundingstring“Optional; default tenth.”ccp_weekly_amountnumber“Optional: the weekly CCP amount; its fee is the amount ÷ 3.”prior_paymentsnumber“Optional: dollars already paid on these periods.”prior_counsel_feesarray“Optional: each prior counsel's dollar share of the fee.”
- list_hearing_notes
“Signed-in Pro or Firm attorneys only.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
fromstring“Optional.”tostring“Optional.”statusstring“queued (default): waiting to be posted.”limitinteger“At most this many (default 20).”
- get_hearing_note
“Signed-in Pro or Firm attorneys only.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
idstringrequired“The note id from list_hearing_notes.”target_systemstring“Optional.”
- mark_hearing_note_posted
“Signed-in Pro or Firm attorneys only.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
3 inputs, 2 required
idstringrequired“The note id.”systemstringrequired“Where it was posted.”external_refstring“Optional.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-14.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 78% of 122
- Tools with a description
- 100% of 32
- Typical description length
- 648 characters
The tool set
Counted from the listing
- Tools
- 32
- Size of the list
- about 12,860 tokens for an agent to load (characters ÷ 4)
- Naming
- 32 of 32 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 32 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-14 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"nys-workers-comp-hub": {
"url": "https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"nys-workers-comp-hub": {
"type": "http",
"url": "https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"nys-workers-comp-hub","type":"http","url":"https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp"}'Claude Code
claude mcp add --transport http nys-workers-comp-hub https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"nys-workers-comp-hub": {
"type": "streamableHttp",
"url": "https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"nys-workers-comp-hub": {
"httpUrl": "https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.nys-workers-comp-hub] url = "https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"nys-workers-comp-hub": {
"url": "https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-14. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-14. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-14. Source: read 2026-11-14.
- Cline marketplace. Not in the Cline marketplace on 2026-11-14. Source: read 2026-11-14.
Own host
- security.txt. No security.txt at https://ltibymvlytodkemdeeox.supabase.co/.well-known/ (HTTP 404, 2026-11-14). No security.txt at https://thecompdesk.com/.well-known/ (HTTP 404, 2026-11-14). Source: ltibymvlytodkemdeeox.supabase.co/.well-known/security.txt · read 2026-11-14.
- A2A agent card. No A2A agent card at https://ltibymvlytodkemdeeox.supabase.co/.well-known/ (HTTP 404, 2026-11-14). No A2A agent card at https://thecompdesk.com/.well-known/ (HTTP 404, 2026-11-14). Source: ltibymvlytodkemdeeox.supabase.co/.well-known/agent-card.json · read 2026-11-14.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint ltibymvlytodkemdeeox.supabase.co/functions/v1/nys-workers-comp-hub/mcp | Session opened | matches | our test · 2026-11-14 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-14 |
| Repository github.com/jmays2294-creator/nys-workers-comp-hub | Opens publicly | matches | api.github.com · 2026-11-14 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- com.thecompdesk · 2 servers
- GitHub owner
- a personal account (jmays2294-creator)
- Repository
- github.com/jmays2294-creator/nys-workers-comp-hub
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-14; security policy read from GitHub · 2026-11-14.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-14 (security policy 2026-11-14). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.thecompdesk/nys-workers-comp-hub
Answered from the data aboveWho publishes com.thecompdesk/nys-workers-comp-hub?
The registry ties the namespace com.thecompdesk to the domain thecompdesk.com; only its owner can publish under it. Its linked repository is github.com/jmays2294-creator/nys-workers-comp-hub; GitHub reports its owner as jmays2294-creator, a personal account. These are facts from the registry and GitHub, not a rating.
Is com.thecompdesk/nys-workers-comp-hub safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does com.thecompdesk/nys-workers-comp-hub need an API key or sign-in?
It opened a session without any credential on 2026-11-14. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.thecompdesk/nys-workers-comp-hub been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Does com.thecompdesk/nys-workers-comp-hub publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of com.thecompdesk/nys-workers-comp-hub?
In github.com/jmays2294-creator/nys-workers-comp-hub, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-14, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 652 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 32 tools, 0 resources, 0 prompts.
- 2,094 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.thecompdesk/nys-workers-comp-hub: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/com.thecompdesk/nys-workers-comp-hub
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.thecompdesk/nys-workers-comp-hub)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology