Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Netwise Paycheck Calculator is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
3
tools declared
remote
at its publisher
—
calls last 7d
What it does
2026 paycheck after taxes
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http netwise-paycheck-calculator-mcp https://paycheck-calculator.zovo.one/mcp
# 2 — ask your agent for something these tools do
# calculate_paycheck, compare_paychecks, calculate_gross_up
Netwise Paycheck Calculator costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 63 servers
theluckystrike63 servers
13 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http netwise-paycheck-calculator-mcp https://paycheck-calculator.zovo.one/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| annual_salary | number | no | Yearly salary before taxes in USD, e.g. 85000. Give this, or hourly_rate, or gross_per_paycheck. |
| hourly_rate | number | no | Hourly wage in USD, e.g. 22 for $22 an hour. Combine with hours_per_week. |
| hours_per_week | number | no | Regular hours worked per week for hourly pay, e.g. 40. Defaults to 40. |
| overtime_hours_per_week | number | no | Overtime hours per week paid at overtime_multiplier, e.g. 5. Defaults to 0. |
| overtime_multiplier | number | no | Overtime pay multiplier, e.g. 1.5 for time-and-a-half (default) or 2 for double time. |
| gross_per_paycheck | number | no | Gross pay per paycheck in USD before any deductions, e.g. 3200. Use instead of a salary or hourly rate. |
| pay_frequency | string | no | How often you are paid: weekly (52), biweekly (26, every two weeks, default), semimonthly (24, twice a month), monthly (12). |
| filing_status | string | no | Form W-4 Step 1(c) filing status: single (or married filing separately, default), married (filing jointly), head_of_household. |
| w4_step2_checked | boolean | no | True if the Form W-4 Step 2 box is checked (two jobs, or married and the spouse also works). Default false. |
| children_under_17 | integer | no | Qualifying children under 17 for W-4 Step 3 ($2,200 each in 2026), e.g. 2. Ignored if w4_step3_amount is given. |
| other_dependents | integer | no | Other dependents for W-4 Step 3 ($500 each), e.g. 1. |
| w4_step3_amount | number | no | Total dollar amount on W-4 Step 3 (dependents and other credits), e.g. 4400. |
| w4_step4a_other_income | number | no | W-4 Step 4(a) other income per year (not from jobs), e.g. 2000. |
| w4_step4b_deductions | number | no | W-4 Step 4(b) deductions per year, e.g. 5000. |
| w4_step4c_extra_withholding | number | no | W-4 Step 4(c) extra federal withholding per paycheck, e.g. 50. |
| claim_overtime_deduction | boolean | no | 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 h |
| k401_percent | number | no | Traditional (pre-tax) 401(k) or 403(b) contribution as a percent of gross pay, e.g. 6 for 6%. |
| k401_per_paycheck | number | no | Traditional 401(k) contribution in dollars per paycheck, e.g. 200. Use instead of k401_percent. |
| roth_401k_percent | number | no | Roth 401(k) (after-tax) contribution as a percent of gross pay, e.g. 4. |
| hsa_per_paycheck | number | no | HSA contribution through payroll per paycheck in USD, e.g. 75. |
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | object | no | Scenario A in full, e.g. {annual_salary: 95000, state: 'TX', pay_frequency: 'biweekly', label: 'Austin'}. |
| b | object | no | 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. |
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. Return
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_net_per_paycheck | number | no | Wanted take-home pay per paycheck in USD, e.g. 2000. |
| target_net_per_year | number | no | Wanted take-home pay per year in USD, e.g. 60000. Use instead of target_net_per_paycheck. |
| hours_per_week | number | no | Regular hours worked per week for hourly pay, e.g. 40. Defaults to 40. |
| pay_frequency | string | no | How often you are paid: weekly (52), biweekly (26, every two weeks, default), semimonthly (24, twice a month), monthly (12). |
| filing_status | string | no | Form W-4 Step 1(c) filing status: single (or married filing separately, default), married (filing jointly), head_of_household. |
| w4_step2_checked | boolean | no | True if the Form W-4 Step 2 box is checked (two jobs, or married and the spouse also works). Default false. |
| children_under_17 | integer | no | Qualifying children under 17 for W-4 Step 3 ($2,200 each in 2026), e.g. 2. Ignored if w4_step3_amount is given. |
| other_dependents | integer | no | Other dependents for W-4 Step 3 ($500 each), e.g. 1. |
| w4_step3_amount | number | no | Total dollar amount on W-4 Step 3 (dependents and other credits), e.g. 4400. |
| w4_step4a_other_income | number | no | W-4 Step 4(a) other income per year (not from jobs), e.g. 2000. |
| w4_step4b_deductions | number | no | W-4 Step 4(b) deductions per year, e.g. 5000. |
| w4_step4c_extra_withholding | number | no | W-4 Step 4(c) extra federal withholding per paycheck, e.g. 50. |
| k401_percent | number | no | Traditional (pre-tax) 401(k) or 403(b) contribution as a percent of gross pay, e.g. 6 for 6%. |
| roth_401k_percent | number | no | Roth 401(k) (after-tax) contribution as a percent of gross pay, e.g. 4. |
| hsa_per_paycheck | number | no | HSA contribution through payroll per paycheck in USD, e.g. 75. |
| health_insurance_per_paycheck | number | no | Pre-tax (section 125) health, dental and vision premiums and FSA per paycheck in USD, e.g. 120. |
| state | string | no | US state where you work and live, as a code or name, e.g. CA, Texas, New Jersey, NYC. Omit for federal only. |
| locality | string | no | 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. |
| state_allowances | integer | no | Allowances or exemptions claimed on the state withholding form (state W-4), e.g. 1. Defaults depend on the state. |
| state_filing_status | string | no | State withholding form status when it differs from the federal one, e.g. NJ 'B', CT 'A', AZ '2.0' (percent). Usually omit. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Netwise Paycheck Calculator or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest935a923dcfec1e3e801a4b45a9ee09c852a4d6bd4863dcac3ce6cc86b42c750a
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| calculate_paycheck | no tags | |
| compare_paychecks | no tags | |
| calculate_gross_up | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest935a923dcfec1e3e
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Netwise Paycheck Calculator can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.