Netwise Paycheck Calculator
REMOTE · PAYCHECK-CALCULATOR.ZOVO.ONE
2026 paycheck after taxes
Available components
Last scanned (47 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability68
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2583 tokens (~645/item across 4 items; 3 tools + 1 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 Management3
- Stability observed for 1 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Supports UI / widget rendering.Pass
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.
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 72
First indexed and scored.
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 23 Oct 2026 · Probed https://paycheck-calculator.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a73f56ff988f8683138c8f14934ce73e |
| SANs: zovo.one, paycheck-calculator.zovo.one, *.paycheck-calculator.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of paycheck-calculator.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | 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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://paycheck-calculator.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://paycheck-calculator.zovo.one/mcp | HTTPS enforced | 301 | https://paycheck-calculator.zovo.one/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 →
calculate_gross_up Find salary for a take-home target ~960
Use this when the user knows the take-home pay they want and asks what salary or hourly rate they need in 2026, e.g. 'what salary do I need to take home $5,000 a month in New Jersey' or 'gross up $2,000 net biweekly'. Solves for the gross pay whose net pay after federal withholding, FICA, state taxes and the given deductions meets the target, using the same 2026 rules as calculate_paycheck. Returns the annual salary, the gross per check, the hourly equivalent if hours_per_week is given, and the full breakdown. Does not gross up bonuses or supplemental wages.
| Name | Type | Req | Description |
|---|---|---|---|
| children_under_17 | integer | – | Qualifying children under 17 for W-4 Step 3 ($2,200 each in 2026), e.g. 2. Ignored if w4_step3_amount is given. |
| filing_status | string | – | Form W-4 Step 1(c) filing status: single (or married filing separately, default), married (filing jointly), head_of_household. |
| health_insurance_per_paycheck | number | – | Pre-tax (section 125) health, dental and vision premiums and FSA per paycheck in USD, e.g. 120. |
| hours_per_week | number | – | Regular hours worked per week for hourly pay, e.g. 40. Defaults to 40. |
| hsa_per_paycheck | number | – | HSA contribution through payroll per paycheck in USD, e.g. 75. |
| k401_percent | number | – | Traditional (pre-tax) 401(k) or 403(b) contribution as a percent of gross pay, e.g. 6 for 6%. |
| label | string | – | Short name for this scenario, e.g. 'Austin offer' or '401k at 10%'. |
| locality | string | – | Optional local tax area where the state supports it, e.g. nyc, yonkers, philadelphia, or a Maryland or Indiana county such as montgomery or marion. |
| other_dependents | integer | – | Other dependents for W-4 Step 3 ($500 each), e.g. 1. |
| pay_frequency | string | – | How often you are paid: weekly (52), biweekly (26, every two weeks, default), semimonthly (24, twice a month), monthly (12). |
| roth_401k_percent | number | – | Roth 401(k) (after-tax) contribution as a percent of gross pay, e.g. 4. |
| state | string | – | US state where you work and live, as a code or name, e.g. CA, Texas, New Jersey, NYC. Omit for federal only. |
| state_additional_withholding | number | – | Extra state withholding per paycheck in USD, e.g. 20. |
| state_allowances | integer | – | Allowances or exemptions claimed on the state withholding form (state W-4), e.g. 1. Defaults depend on the state. |
| state_filing_status | string | – | State withholding form status when it differs from the federal one, e.g. NJ 'B', CT 'A', AZ '2.0' (percent). Usually omit. |
| target_net_per_paycheck | number | – | Wanted take-home pay per paycheck in USD, e.g. 2000. |
| target_net_per_year | number | – | Wanted take-home pay per year in USD, e.g. 60000. Use instead of target_net_per_paycheck. |
| w4_step2_checked | boolean | – | True if the Form W-4 Step 2 box is checked (two jobs, or married and the spouse also works). Default false. |
| w4_step3_amount | number | – | Total dollar amount on W-4 Step 3 (dependents and other credits), e.g. 4400. |
| w4_step4a_other_income | number | – | W-4 Step 4(a) other income per year (not from jobs), e.g. 2000. |
| w4_step4b_deductions | number | – | W-4 Step 4(b) deductions per year, e.g. 5000. |
| w4_step4c_extra_withholding | number | – | W-4 Step 4(c) extra federal withholding per paycheck, e.g. 50. |
| ytd_gross_before_this_check | number | – | Gross pay already received from this job earlier in 2026, e.g. 150000. Only matters near the Social Security wage base or the $200,000 Additional Medicare threshold. |
| Name | Type | Req | Description |
|---|---|---|---|
| annual_salary_needed | number | yes | – |
| checks_per_year | number | yes | – |
| downloads | object | yes | – |
| effective_federal_rate | number | yes | – |
| effective_state_rate | number|null | yes | – |
| effective_tax_rate | number | yes | – |
| federal_bracket | number | yes | – |
| gross_per_check | number | yes | – |
| gross_per_year | number | yes | – |
| hourly_rate_needed | number|null | yes | – |
| label | string | yes | – |
| lines | array | yes | – |
| net_per_check | number | yes | – |
| net_per_year | number | yes | – |
| notes | array | yes | – |
| pay_frequency | string | yes | – |
| state | string|null | yes | – |
| state_method | string | yes | – |
| state_supported | boolean | yes | – |
| target_net_per_check | number | yes | – |
| taxes_per_check | number | yes | – |
| taxes_per_year | number | yes | – |
No examples provided.
calculate_paycheck Calculate take-home pay ~1,249
Use this when the user asks 'how much is my paycheck after taxes', wants a paycheck calculator or take home pay calculator for a US job in 2026, or asks what a salary or hourly wage is after tax (e.g. '85k salary after taxes in California', 'what is 75000 a year biweekly after taxes', '$22 an hour 40 hours', 'how much tax comes out of my paycheck'). Computes federal income tax withholding with the IRS Pub. 15-T 2026 percentage method and Form W-4 inputs, Social Security, Medicare, Additional Medicare, state income tax and state payroll taxes (e.g. CA SDI, NJ FLI, WA Cares), pre-tax 401(k)/HSA/health premiums, net pay per check and per year, and effective rates. Returns a PDF estimate and a CSV with one row per 2026 paycheck. Does not run payroll, file tax returns, or produce pay stubs. Do not use to make a pay stub or proof of income.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_salary | number | – | Yearly salary before taxes in USD, e.g. 85000. Give this, or hourly_rate, or gross_per_paycheck. |
| children_under_17 | integer | – | Qualifying children under 17 for W-4 Step 3 ($2,200 each in 2026), e.g. 2. Ignored if w4_step3_amount is given. |
| claim_overtime_deduction | boolean | – | True to add the 2026 qualified overtime deduction (the 'half' of time-and-a-half, up to $12,500 or $25,000 married) to W-4 Step 4(b), as the 2026 W-4 worksheet allows. Needs hourly_rate and overtime… |
| filing_status | string | – | Form W-4 Step 1(c) filing status: single (or married filing separately, default), married (filing jointly), head_of_household. |
| gross_per_paycheck | number | – | Gross pay per paycheck in USD before any deductions, e.g. 3200. Use instead of a salary or hourly rate. |
| health_insurance_per_paycheck | number | – | Pre-tax (section 125) health, dental and vision premiums and FSA per paycheck in USD, e.g. 120. |
| hourly_rate | number | – | Hourly wage in USD, e.g. 22 for $22 an hour. Combine with hours_per_week. |
| hours_per_week | number | – | Regular hours worked per week for hourly pay, e.g. 40. Defaults to 40. |
| hsa_per_paycheck | number | – | HSA contribution through payroll per paycheck in USD, e.g. 75. |
| k401_per_paycheck | number | – | Traditional 401(k) contribution in dollars per paycheck, e.g. 200. Use instead of k401_percent. |
| k401_percent | number | – | Traditional (pre-tax) 401(k) or 403(b) contribution as a percent of gross pay, e.g. 6 for 6%. |
| label | string | – | Short name for this scenario, e.g. 'Austin offer' or '401k at 10%'. |
| locality | string | – | Optional local tax area where the state supports it, e.g. nyc, yonkers, philadelphia, or a Maryland or Indiana county such as montgomery or marion. |
| other_dependents | integer | – | Other dependents for W-4 Step 3 ($500 each), e.g. 1. |
| overtime_hours_per_week | number | – | Overtime hours per week paid at overtime_multiplier, e.g. 5. Defaults to 0. |
| overtime_multiplier | number | – | Overtime pay multiplier, e.g. 1.5 for time-and-a-half (default) or 2 for double time. |
| pay_frequency | string | – | How often you are paid: weekly (52), biweekly (26, every two weeks, default), semimonthly (24, twice a month), monthly (12). |
| roth_401k_percent | number | – | Roth 401(k) (after-tax) contribution as a percent of gross pay, e.g. 4. |
| state | string | – | US state where you work and live, as a code or name, e.g. CA, Texas, New Jersey, NYC. Omit for federal only. |
| state_additional_withholding | number | – | Extra state withholding per paycheck in USD, e.g. 20. |
| state_allowances | integer | – | Allowances or exemptions claimed on the state withholding form (state W-4), e.g. 1. Defaults depend on the state. |
| state_filing_status | string | – | State withholding form status when it differs from the federal one, e.g. NJ 'B', CT 'A', AZ '2.0' (percent). Usually omit. |
| w4_step2_checked | boolean | – | True if the Form W-4 Step 2 box is checked (two jobs, or married and the spouse also works). Default false. |
| w4_step3_amount | number | – | Total dollar amount on W-4 Step 3 (dependents and other credits), e.g. 4400. |
| w4_step4a_other_income | number | – | W-4 Step 4(a) other income per year (not from jobs), e.g. 2000. |
| w4_step4b_deductions | number | – | W-4 Step 4(b) deductions per year, e.g. 5000. |
| w4_step4c_extra_withholding | number | – | W-4 Step 4(c) extra federal withholding per paycheck, e.g. 50. |
| ytd_gross_before_this_check | number | – | Gross pay already received from this job earlier in 2026, e.g. 150000. Only matters near the Social Security wage base or the $200,000 Additional Medicare threshold. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks_per_year | number | yes | – |
| downloads | object | yes | – |
| effective_federal_rate | number | yes | – |
| effective_state_rate | number|null | yes | – |
| effective_tax_rate | number | yes | – |
| federal_bracket | number | yes | – |
| gross_per_check | number | yes | – |
| gross_per_year | number | yes | – |
| label | string | yes | – |
| lines | array | yes | – |
| net_per_check | number | yes | – |
| net_per_year | number | yes | – |
| notes | array | yes | – |
| pay_frequency | string | yes | – |
| state | string|null | yes | – |
| state_method | string | yes | – |
| state_supported | boolean | yes | – |
| taxes_per_check | number | yes | – |
| taxes_per_year | number | yes | – |
No examples provided.
compare_paychecks Compare two paychecks ~250
Use this when the user wants to compare take-home pay for two US paycheck scenarios in 2026 side by side: 'should I take the job in Texas or California after taxes', two job offers in different states or cities, a raise, a different pay frequency, or 'how much more per paycheck if I raise my 401k to 10%'. Give scenario a in full and scenario b with only the fields that change (everything else is copied from a). Returns both breakdowns (federal withholding, FICA, state taxes, net per check and per year) and the difference, plus a side-by-side PDF and a CSV. Does not compare cost of living, benefits, or run payroll.
| Name | Type | Req | Description |
|---|---|---|---|
| a | object | – | Scenario A in full, e.g. {annual_salary: 95000, state: 'TX', pay_frequency: 'biweekly', label: 'Austin'}. |
| b | object | – | Scenario B: only the fields that differ from A, e.g. {annual_salary: 110000, state: 'NY', locality: 'nyc', label: 'NYC'}. Set a field to null to remove it from B. |
| Name | Type | Req | Description |
|---|---|---|---|
| a | object | yes | – |
| b | object | yes | – |
| difference | object | yes | – |
| downloads | object | yes | – |
| notes | array | yes | – |
No examples provided.
How do I install the Netwise Paycheck Calculator MCP server?
Netwise Paycheck Calculator is a hosted endpoint at https://paycheck-calculator.zovo.one/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 · paycheck-calculator.zovo.one
claude mcp add --transport http theluckystrike-paycheck-calculator 'https://paycheck-calculator.zovo.one/mcp'
What is the Netwise Paycheck Calculator MCP server?
Netwise Paycheck Calculator is an MCP server listed in the public MCP registry as io.github.theluckystrike/paycheck-calculator. 2026 paycheck after taxes. This page covers its hosted endpoint (https://paycheck-calculator.zovo.one/mcp).
Is the Netwise Paycheck Calculator MCP server safe to use?
Netwise Paycheck Calculator scores 73 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 Netwise Paycheck Calculator MCP server expose?
Netwise Paycheck Calculator exposes 3 tools: calculate_paycheck, compare_paychecks, calculate_gross_up. Their descriptions and schemas cost roughly 2,459 tokens of context every time the server is loaded.
Does the Netwise Paycheck Calculator MCP server require authentication?
No. We connected to Netwise Paycheck Calculator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Netwise Paycheck Calculator MCP server still maintained?
Netwise Paycheck Calculator is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.