TeamPredict HR Calculators
REMOTE · WWW.TEAMPREDICT.AI
HR, payroll and date calculators: turnover, eNPS, US take-home pay, bonus tax, overtime. No key.
Available components
Last scanned (14 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6671 tokens (~303/item across 22 items; 22 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "severance_pay" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://www.teampredict.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.teampredict.ai | CN=YR2,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 5f927c454093fb35759e28911a632d900a1 |
| SANs: www.teampredict.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 www.teampredict.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| teampredict.ai. | 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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.teampredict.ai/mcp | Verified | 200 | |
| http (plaintext) | http://www.teampredict.ai/mcp | HTTPS enforced | 308 | https://www.teampredict.ai/mcp |
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 →
add_business_days Add or subtract business days ~239
Find the date that is a given number of business days after (or before) a start date, skipping weekends and optionally US federal holidays. Use it to answer 'what is the due date 10 business days from now?', delivery dates, response deadlines and notice periods. Use business_days_between instead to count the working days between two known dates, and add_to_date to move by calendar years, months, weeks or days. The start date itself is not counted; day 1 is the next business day. Holidays are the 11 US federal holidays with observed dates. Valid for years 2000 to 2100.
| Name | Type | Req | Description |
|---|---|---|---|
| business_days | integer | yes | How many business days to move, a whole number from 0 to 10,000. |
| direction | string | – | add to move forward in time, subtract to move back. Default add. |
| skip_us_federal_holidays | boolean | – | Whether US federal holidays are skipped as well as weekends. Default true. |
| start_date | string | yes | The date to count from as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
add_time_to_datetime Add or subtract days, hours and minutes from a date-time ~294
Move a date and clock time forward or back by days, hours and minutes in a US time zone and get the resulting date and time. Days move the calendar date and keep the clock time (the way a phone calendar does); hours and minutes are counted as they really pass, so a daylight saving change inside the span is handled. Use time_duration_between instead to measure the gap between two known date-times, add_to_date for calendar years, months and weeks, and convert_time_zone to show a moment in other zones.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to move. Default 0. |
| direction | string | – | add to move forward, subtract to move back. Default add. |
| hours | integer | – | Hours to move. Default 0. |
| minutes | integer | – | Minutes to move. Default 0. |
| start_date | string | yes | The date to start from as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| start_time | string | yes | The time to start from as a 24-hour clock time in the form HH:MM, for example 22:30. |
| time_zone | string | – | The time zone the clock times are read in, so a span across a daylight saving change counts the hour that really passes. Use 'none' for plain 24-hour days with no zone. Default America/New_York. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
add_to_date Add or subtract time from a date ~263
Add or subtract years, months, weeks and days to or from a calendar date and get the resulting date with its weekday, ISO week and day of the year. Use it for 'what is the date 90 days from today?', contract end dates, probation periods and anniversaries. Years and months move by the calendar first (Jan 31 plus one month is the last day of February), then weeks and days. Use add_business_days to skip weekends and holidays and days_between_dates to measure the gap between two dates. Valid for years 2000 to 2100.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to move, 0 to 37,000. Default 0. |
| direction | string | – | add to move forward, subtract to move back. Default add. |
| months | integer | – | Months to move, 0 to 1,200. Default 0. |
| start_date | string | yes | The date to start from as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| weeks | integer | – | Weeks to move, 0 to 5,300. Default 0. |
| years | integer | – | Years to move, 0 to 100. Default 0. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
business_days_between Business days between two dates ~240
Count the business days (Monday to Friday, optionally skipping US federal holidays) between two dates. Use it for working-day questions such as notice periods, delivery windows, payroll runs and project lead times. Use add_business_days instead to find the date that is N business days from a start date, and days_between_dates for plain calendar days. Holidays are the 11 US federal holidays with their observed dates when one falls on a weekend; company and state holidays are not included. Valid for years 2000 to 2100.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | The second date; if it is before start_date the two are swapped as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| include_end_date | boolean | – | Whether the end date itself is counted when it is a business day. Default true. |
| skip_us_federal_holidays | boolean | – | Whether US federal holidays are left out of the business-day count. Default true. |
| start_date | string | yes | The first date as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
convert_time_zone Time zone converter ~259
Convert one date and clock time from a source time zone to other time zones, with daylight saving applied for that date, and find the stretch of the day when it is 9 AM to 5 PM in every zone at once. Use it to schedule across offices, pick a meeting time for a distributed team, or answer 'what is 3 PM Eastern in London?'. Supports 24 zones (US zones, UTC and major world zones); the valid zone ids are listed in the schema. Use time_duration_between for the length of time between two moments.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The date in the source time zone as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| from_time_zone | string | – | IANA id of the source time zone. Default America/New_York. |
| time | string | yes | The clock time in the source time zone as a 24-hour clock time in the form HH:MM, for example 22:30. |
| to_time_zones | array | yes | IANA ids of the zones to convert to, between 1 and 12 (for example ["America/Los_Angeles","Europe/London","Asia/Kolkata"]). |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
cost_of_a_bad_hire Cost of a bad hire ~323
Estimate the total cost of one bad hire: the salary paid for lost productivity plus recruiting, onboarding, manager time, severance and the cost of hiring a replacement. Use it for a single failed hire with a known salary and tenure. Use employee_turnover_cost instead for the company-wide cost of turnover across many employees, and severance_pay for the pay owed to a departing employee. Every cost line is optional and defaults to the TeamPredict calculator's default; set a line to 0 to leave it out.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_salary_usd | number | yes | Annual salary of the role, in US dollars. |
| lost_productivity_percent | number | – | Share of the salary paid during the tenure that bought no useful work, 0 to 100. Default 60. |
| manager_time_cost_usd | number | – | Value of manager and team time spent on the hire, in US dollars. Default 4000. |
| months_employed | number | yes | Months the hire stayed before leaving or being let go, 0 to 120. |
| onboarding_cost_usd | number | – | Onboarding and training cost, in US dollars. Default 3000. |
| recruiting_cost_usd | number | – | Recruiting and agency cost, in US dollars. Default 5000. |
| rehire_cost_usd | number | – | Cost of finding and hiring the replacement, in US dollars. Default 8000. |
| severance_and_exit_cost_usd | number | – | Severance and exit cost, in US dollars. Default 5000. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
days_between_dates Days between two dates ~196
Count the calendar days between two dates and break the gap into weeks, months and years, with the weekdays and weekend days inside it. Use it for 'how many days until X', tenure, age of a record, notice periods in calendar days and countdowns. Use business_days_between instead to leave out weekends and federal holidays, and time_duration_between when clock times matter. Valid for years 2000 to 2100.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | The second date; if it is before start_date the two are swapped as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| include_end_date | boolean | – | Whether the end date itself counts as a day, which adds one to the total. Default false. |
| start_date | string | yes | The first date as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
employee_retention_rate Employee retention rate ~196
Calculate the employee retention rate exactly, by separating leavers who were on the payroll at the start of the period from leavers who were hired during it. Use it when you can tell those two groups of leavers apart; it returns the standard retention rate, the new-hire retention rate, the turnover rate and the ending headcount, and shows why retention and turnover do not add up to 100%. Use employee_turnover_rate instead when you only have one total for people who left.
| Name | Type | Req | Description |
|---|---|---|---|
| leavers_from_new_hires | integer | yes | Leavers who were hired during the period. Cannot exceed new_hires. |
| leavers_from_starting_group | integer | yes | Leavers who were already on the payroll when the period opened. Cannot exceed starting_headcount. |
| new_hires | integer | yes | People hired during the period. |
| starting_headcount | integer | yes | Employees on the payroll when the period opened. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
employee_turnover_cost Employee turnover cost ~294
Estimate what employee turnover costs a company per year, and how much cutting turnover would save. Use it when you know headcount, average salary and the annual turnover rate and want the dollar cost of people leaving. Use employee_turnover_rate instead to work out the turnover rate itself from headcounts and leavers, and cost_of_a_bad_hire for the cost of one specific failed hire. Returns departures per year, cost per departure, total annual cost and the yearly saving from a given cut in turnover. Same formula as the TeamPredict turnover cost calculator.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_turnover_rate_percent | number | yes | Share of employees who leave in a year, as a percentage from 0 to 100. 15 means 15%. |
| average_salary_usd | number | yes | Average annual salary per employee, in US dollars. For example 70000. |
| employees | integer | yes | Number of employees (headcount), a whole number from 1 to 1,000,000. |
| replacement_cost_percent_of_salary | number | – | What replacing one person costs, as a percentage of their annual salary. 50 means half a year of pay, which is the calculator's default; published estimates range from about 30 to 200. |
| target_reduction_points | number | – | Percentage points of annual turnover you want to cut, for the savings figure. Capped at the turnover rate. Default 3. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
employee_turnover_rate Employee turnover rate ~206
Calculate the employee turnover (attrition) rate for a month, quarter or year from starting headcount, ending headcount and the number of people who left. Use it when you have headcounts and separations and need the rate; it also annualizes a monthly or quarterly rate. Use employee_retention_rate instead when you can split leavers into people who were there at the start and people hired during the period, and employee_turnover_cost to price the turnover in dollars. Returns the turnover rate for the period, the annualized rate, average headcount and a simple retention rate.
| Name | Type | Req | Description |
|---|---|---|---|
| ending_headcount | integer | yes | Employees on the payroll at the end of the period. |
| period | string | – | The length of the measurement period: month, quarter or year. Default year. |
| separations | integer | yes | People who left during the period, voluntarily or not. |
| starting_headcount | integer | yes | Employees on the payroll at the start of the period. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
enps_score Employee Net Promoter Score (eNPS) ~163
Calculate an employee Net Promoter Score (eNPS) from survey response counts: the percentage of promoters minus the percentage of detractors, from -100 to +100. Use it when you have the count of people who answered 9-10 (promoters), 7-8 (passives) and 0-6 (detractors) to the question 'How likely are you to recommend working here?'. Returns the score, both percentages and a rule-of-thumb reading (not a universal benchmark).
| Name | Type | Req | Description |
|---|---|---|---|
| detractors | integer | yes | Number of responses scoring 0 to 6. |
| passives | integer | yes | Number of responses scoring 7 or 8. |
| promoters | integer | yes | Number of responses scoring 9 or 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
fte_calculator Full-time equivalent (FTE) and ACA count ~206
Count full-time equivalent employees (FTE) from full-time staff and groups of part-time staff, and run the Affordable Care Act count that decides whether an employer has 50 or more full-time equivalents. Use it for workforce planning, headcount reporting or checking applicable-large-employer status. FTE is total weekly hours divided by the hours of one full-time schedule; the ACA count uses the IRS rule (30 hours a week is full-time, other employees count their monthly hours up to 120 each, divided by 120). Returns both counts; assumes every month looks like the one entered.
| Name | Type | Req | Description |
|---|---|---|---|
| full_time_employees | integer | yes | Number of full-time employees. |
| full_time_hours_per_week | number | – | Weekly hours of one full-time schedule at your company. Default 40. |
| part_time_groups | array | – | Up to 6 groups of part-time staff, each with a head count and weekly hours per person. Leave empty if there are none. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
hourly_to_salary Hourly to salary converter ~281
Convert pay between hourly, daily, weekly, biweekly, semimonthly, monthly and yearly, in either direction, from one amount. Use it for 'what is $25 an hour per year?' or 'what is $90,000 a year per hour?'. It uses hours per week and paid weeks per year (default 40 hours and 52 weeks), so a 2,080-hour year is the default. Amounts are gross, before tax. Use us_paycheck_take_home for take-home pay after tax and overtime_pay for pay that includes overtime hours.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | The pay you know, in US dollars for the period named by period. |
| days_per_week | number | – | Days worked in a week, for the per-day figure. Default 5. |
| hours_per_week | number | – | Hours worked in a paid week. Default 40. |
| paid_weeks_per_year | number | – | Paid weeks in a year; use 50 or 48 to leave out unpaid vacation. Default 52. |
| period | string | – | The period that amount_usd is paid per: hour, day, week, biweekly (every two weeks, 26 a year), semimonthly (twice a month, 24 a year), month or year. Default hour. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
military_shift_hours Hours between two military times ~176
Find how long a shift or interval lasts between a start and an end written in military (24-hour) time, including shifts that run past midnight (2200 to 0630 is 8 hours 30 minutes). An end at or before the start counts as the next day. Returns hours and minutes and decimal hours for timesheets. Use military_time_convert to translate a single time between 24-hour and AM/PM, and time_duration_between when the two moments have different dates or a time zone with daylight saving.
| Name | Type | Req | Description |
|---|---|---|---|
| end_military_time | string | yes | The end in military time, for example 0630 or 06:30. At or before the start means the next day. |
| start_military_time | string | yes | The start in military time, for example 2200 or 22:00. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
military_time_convert Military (24-hour) time converter ~234
Convert between military (24-hour) time and standard 12-hour AM/PM time, in either direction. Give military_time (for example 1345, 13:45 or 0800) to get the standard time, or hour_12, minute and period to get the military time. Returns the converted time in every common written form, the plain-English name for special times (midnight, noon) and the hour of the military-time chart it sits in. Use military_shift_hours instead to find how many hours run between two military times.
| Name | Type | Req | Description |
|---|---|---|---|
| hour_12 | integer | – | The hour on a 12-hour clock, 1 to 12. Use with period (and minute). |
| military_time | string | – | A military time such as 1345, 13:45, 945 or 2400 (end of day). Give this, or hour_12 with period. |
| minute | integer | – | The minute, 0 to 59, used with hour_12. Default 0. |
| period | string | – | AM or PM, used with hour_12. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
overtime_pay Overtime pay ~325
Calculate a week of overtime pay at time and a half under the federal FLSA rule (hours over 40 in the week) or California's rules (daily overtime over 8 hours, double time over 12, the seventh consecutive day, and the weekly 40). Use rule_set federal with total hours worked in the week and any extra pay that counts toward the regular rate, such as a nondiscretionary bonus; use rule_set california with the hours worked on each of the seven days. Returns regular and overtime hours and pay and the week's total, gross before tax. Use us_paycheck_take_home with overtime_hours_per_week for take-home pay including overtime, and hourly_to_salary for converting pay without overtime.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_hours | array | – | Hours worked on each day of the workweek, in order, up to 7 entries (california rule_set only). The seventh day counts as the seventh consecutive day only when all seven days have hours. |
| extra_pay_usd | number | – | Extra pay for the week that counts toward the regular rate, such as a nondiscretionary bonus, in US dollars (federal rule_set only). Default 0. |
| hourly_rate_usd | number | yes | Regular hourly rate in US dollars. |
| hours_worked | number | – | Total hours worked in the week (federal rule_set only), 0 to 168. |
| rule_set | string | – | The overtime rules to apply: federal (weekly, over 40 hours) or california (daily, seventh day and weekly). Default federal. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
pto_accrual PTO accrual ~360
Work out how paid time off accrues: hours earned per pay period, per month and per hour worked, plus the balance after each pay period, with an optional balance cap and hours already used. Use it to design or explain a PTO policy, or to project an employee's balance by year end. Accrual pauses while the balance sits at the cap and resumes once time is used. Use hourly_to_salary or salary_increase for pay questions, not this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_pto | number | yes | Paid time off granted per year, in the unit given by unit (for example 15 days or 120 hours). |
| balance_cap_hours | number | – | Maximum PTO balance in hours; accrual pauses at the cap. Leave out for no cap. |
| hours_per_day | number | – | Hours in one working day, used to convert days to hours. Default 8. |
| hours_used_this_year | number | – | PTO hours already taken this year. Default 0. |
| hours_worked_per_year | number | – | Paid hours worked in a year, for the accrual per hour worked. Default 2080 (40 hours x 52 weeks). |
| pay_frequency | string | – | How often accrual is credited: weekly (52 a year), biweekly (26), semimonthly (24) or monthly (12). Default biweekly. |
| pay_periods_completed | integer | – | Pay periods already paid this year, so the balance can be shown as of today. Default 0. |
| starting_balance_hours | number | – | PTO balance in hours at the start of the year. Default 0. |
| unit | string | – | Whether annual_pto is in days or hours. Default days. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
salary_increase Salary increase (pay raise) ~294
Calculate a pay raise: the new annual and hourly pay, the raise per year, month and biweekly paycheck, the raise as a percentage, and whether it keeps up with inflation. Give either raise_percent (a percentage raise on current pay) or new_pay (the new pay, from which the percentage is worked out), and the pay as per year or per hour. Use hourly_to_salary instead to convert between pay periods without a raise, and us_paycheck_take_home for take-home pay after tax. All amounts are before tax.
| Name | Type | Req | Description |
|---|---|---|---|
| current_pay | number | yes | Current pay in US dollars, per year or per hour according to pay_unit. |
| hours_per_week | number | – | Hours worked per week, to move between hourly and yearly pay (52 weeks a year). Default 40. |
| inflation_percent | number | – | Expected yearly inflation as a percentage, to show the raise in real terms. Default 3.7 (US CPI-U, 12 months to September 2026). |
| new_pay | number | – | The new pay in US dollars, per year or per hour according to pay_unit. Give this or raise_percent. |
| pay_unit | string | – | Whether current_pay and new_pay are per year or per hour. Default year. |
| raise_percent | number | – | The raise as a percentage of current pay, for example 4 for 4%. Give this or new_pay. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
severance_pay Severance pay ~373
Estimate a severance package: weeks of pay per year of service times years of service times weekly pay, with an optional plan minimum and maximum, plus unused PTO paid out, employer-paid health coverage and other lump sums. Use it for an employer budgeting an exit or an employee checking an offer; every input is the plan's own terms, because US federal law sets no severance formula. Use cost_of_a_bad_hire for the all-in cost of a failed hire instead. Amounts are before tax.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_salary_usd | number | yes | Annual salary in US dollars; weekly pay is salary divided by 52. |
| health_coverage_months | number | – | Months of health coverage the employer pays. Default 0. |
| maximum_weeks | number | – | The plan's cap in weeks of pay, if any. Trims a long tenure down to this figure; if below the minimum, the cap wins. |
| minimum_weeks | number | – | The plan's minimum severance in weeks of pay, if any. Lifts a short tenure up to this figure. |
| monthly_health_premium_usd | number | – | Monthly cost of that coverage in US dollars. Default 0. |
| other_lump_sums_usd | number | – | Any other lump sums, such as a pro-rated bonus, in US dollars. Default 0. |
| unused_pto_days | number | – | Unused PTO days paid out, valued at salary divided by 260 working days. Default 0. |
| weeks_of_pay_per_year | number | yes | Weeks of pay the plan gives for each year of service. Many plans use 1 or 2; there is no legal standard. |
| years_of_service | number | yes | Years of service, decimals allowed (for example 4.5). |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
time_duration_between Time duration between two date-times ~283
Work out how much time passes between a start and an end date and time, in days, hours and minutes, accounting for daylight saving changes in the chosen US time zone. Use it for shift lengths that cross midnight, elapsed time on a ticket, on-call windows and billing time. Use days_between_dates for whole calendar days, add_time_to_datetime to move a date-time forward or back by a known amount, and military_shift_hours for a shift written in 24-hour times only.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | The end date as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| end_time | string | yes | The end time as a 24-hour clock time in the form HH:MM, for example 22:30. |
| start_date | string | yes | The start date as a calendar date in the form YYYY-MM-DD, for example 2026-11-02. |
| start_time | string | yes | The start time as a 24-hour clock time in the form HH:MM, for example 22:30. |
| time_zone | string | – | The time zone the clock times are read in, so a span across a daylight saving change counts the hour that really passes. Use 'none' for plain 24-hour days with no zone. Default America/New_York. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
us_bonus_tax US bonus tax withholding ~505
Calculate how much tax is withheld from a US bonus in 2026 and what is left: federal income tax (the 22% flat rate or the combined method, 37% above $1 million), Social Security, Medicare, and the state's own bonus withholding rule, for all 50 states and DC. Use it for 'how much of my $X bonus will I keep in <state>?'. Withholding is not the final tax: the bonus is taxed at your normal rate on your return. Use us_paycheck_take_home instead for regular pay, and salary_increase for a raise. When the bonus is paid on its own it also returns the result under the other federal method so the two can be compared.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_salary_usd | number | yes | Regular yearly salary in US dollars, before the bonus. For example 75000. |
| bonus_paid | string | – | Whether the employer pays the bonus as a separate payment (the usual case) or adds it to a regular paycheck. Default separately. |
| bonus_usd | number | yes | Gross bonus in US dollars. For example 5000. |
| earlier_supplemental_pay_usd | number | – | Bonuses and other supplemental pay already paid this calendar year, before this one, in US dollars. Total supplemental pay above $1 million in a year is withheld at 37%. Default 0. |
| federal_method | string | – | How the employer withholds federal income tax on a bonus paid separately: the flat 22% rate (the common choice) or the combined (aggregate) method. Ignored when the bonus is paid with a regular paych… |
| filing_status | string | – | Filing status on the federal Form W-4, step 1(c): single (or married filing separately), married (filing jointly) or head (head of household). Default single. |
| pay_frequency | string | – | How often the employee is paid: weekly (52 paychecks a year), biweekly (26), semimonthly (24, twice a month) or monthly (12). Default biweekly. |
| state | string | yes | Two-letter postal code of the state where the employee works and lives: all 50 states and DC (for example CA, NY, TX, DC). |
| w4_step2_checkbox | boolean | – | The 'multiple jobs or spouse works' box in Form W-4 step 2(c). Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
us_paycheck_take_home US paycheck take-home pay ~875
Calculate US take-home (net) pay from a salary or an hourly wage for 2026, after federal income tax (from the Form W-4), Social Security, Medicare and the state's own income tax and payroll contributions, in any of the 50 states or DC. Use it for 'how much will I take home on $X in <state>?', for comparing states, or to price an offer; it also returns the full-year totals and what the employer pays on top. Use us_bonus_tax instead for tax withheld from a bonus, overtime_pay for the extra pay for overtime hours before tax, and hourly_to_salary for converting pay between hour, week, month and year without tax. Assumes the 2026 federal withholding method and the state's published employer withholding formula, one job, and a W-4 filed in the standard way.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_salary_usd | number | – | Yearly gross salary in US dollars. Required when pay_type is salary. For example 60000. |
| filing_status | string | – | Filing status on the federal Form W-4, step 1(c): single (or married filing separately), married (filing jointly) or head (head of household). Default single. |
| health_premiums_usd_per_paycheck | number | – | Pre-tax health, dental and vision premiums per paycheck, in US dollars. Default 0. |
| hourly_rate_usd | number | – | Hourly wage in US dollars. Required when pay_type is hourly. For example 25. |
| hsa_usd_per_paycheck | number | – | Pre-tax HSA contribution through payroll per paycheck, in US dollars (capped at the 2026 family limit). Default 0. |
| local_tax | string | – | Id of a city or county income tax to include (for example 'nyc' or 'yonkers' for New York). Leave out for none; an unknown id returns the ids that state accepts. |
| overtime_hours_per_week | number | – | Overtime hours per week paid at time and a half, hourly pay only. Default 0. |
| pay_frequency | string | – | How often the employee is paid: weekly (52 paychecks a year), biweekly (26), semimonthly (24, twice a month) or monthly (12). Default biweekly. |
| pay_type | string | – | Whether the employee is paid a yearly salary or an hourly wage. Default salary. |
| regular_hours_per_week | number | – | Regular (straight-time) hours per week, hourly pay only. Default 40. |
| state | string | yes | Two-letter postal code of the state where the employee works and lives: all 50 states and DC (for example CA, NY, TX, DC). |
| state_allowances | integer | – | Allowances or exemptions on the state's own withholding form, for states that have one. Leave out to use the typical single worker's number for that state. |
| traditional_401k_percent | number | – | Pre-tax 401(k) contribution as a percentage of gross pay, 0 to 100 (capped at the 2026 IRS limit). Default 0. |
| w4_children_under_17 | integer | – | Qualifying children under 17 for Form W-4 step 3 (a $2,200 credit each in 2026). Default 0. |
| w4_deductions_usd_per_year | number | – | Deductions above the standard deduction, Form W-4 step 4(b), in US dollars per year. Default 0. |
| w4_extra_withholding_usd_per_paycheck | number | – | Extra federal withholding per paycheck, Form W-4 step 4(c), in US dollars. Default 0. |
| w4_other_dependents | integer | – | Other dependents for Form W-4 step 3 (a $500 credit each). Default 0. |
| w4_other_income_usd_per_year | number | – | Other income not from jobs, Form W-4 step 4(a), in US dollars per year. Default 0. |
| w4_step2_checkbox | boolean | – | The 'multiple jobs or spouse works' box in Form W-4 step 2(c). Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculator_url | string | yes | The TeamPredict calculator page that shows the same calculation, where a person can change the inputs. |
| inputs | object | yes | The inputs as used, with defaults filled in. |
| results | object | yes | The computed numbers. Unavailable numbers are null. |
| summary | string | yes | One or two plain sentences with the headline numbers. |
No examples provided.
How do I install the TeamPredict HR Calculators MCP server?
TeamPredict HR Calculators is a hosted endpoint at https://www.teampredict.ai/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 · www.teampredict.ai
claude mcp add --transport http ai-teampredict-hr-calculators 'https://www.teampredict.ai/mcp'
What is the TeamPredict HR Calculators MCP server?
TeamPredict HR Calculators is an MCP server listed in the public MCP registry as ai.teampredict/hr-calculators. HR, payroll and date calculators: turnover, eNPS, US take-home pay, bonus tax, overtime. No key. This page covers its hosted endpoint (https://www.teampredict.ai/mcp).
Is the TeamPredict HR Calculators MCP server safe to use?
TeamPredict HR Calculators scores 82 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 TeamPredict HR Calculators MCP server expose?
TeamPredict HR Calculators exposes 22 tools: employee_turnover_cost, employee_turnover_rate, employee_retention_rate, cost_of_a_bad_hire, enps_score, and 17 more. Their descriptions and schemas cost roughly 6,585 tokens of context every time the server is loaded.
Does the TeamPredict HR Calculators MCP server require authentication?
No. We connected to TeamPredict HR Calculators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TeamPredict HR Calculators MCP server still maintained?
TeamPredict HR Calculators 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 TeamPredict HR Calculators MCP server?
VerifyMCP ran 13 checks on TeamPredict HR Calculators, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.