Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

StateTakeHome

NPM · STATETAKEHOME-MCP

US take-home pay calculator by state: federal and state tax, FICA, deductions.

Available components

0 this week 76 Trust /100

Last scanned (18 hours ago)

Scores higher than 53% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 835 tokens (~278/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "us_take_home_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 3 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

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

  • 9 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/statetakehome-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~835 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
capital_gains_tax ~289

Computes federal capital gains tax (long-term 0%/15%/20% stacked bands or short-term ordinary rates), the 3.8% Net Investment Income Tax (NIIT) above the MAGI threshold, and an optional state income tax on the gain (states generally tax capital gains as ordinary income). Example input: { "gain": 50000, "ordinaryTaxableIncome": 80000, "filingStatus": "single", "term": "long" }. 2026 tax year — estimates, not tax advice; thresholds from Rev. Proc. 2025-32, cross-checked against Tax Foundation & Schwab.

NameTypeReqDescription
exclusionnumber–Amount excluded from the gain before tax (e.g. the §121 primary-residence sale exclusion).
filingStatusstringyesIRS filing status.
gainnumberyesGross capital gain in USD (sale price minus cost basis), e.g. 50000.
ordinaryTaxableIncomenumberyesOther taxable income (excluding the gain), which sets the long-term capital gains bracket and NIIT threshold.
statestring–Optional two-letter US state or DC postal code; most states tax the gain as ordinary income.
termstringyes"long" for assets held > 1 year (preferential rates), "short" for ordinary rates.

No output schema declared.

No examples provided.

self_employment_tax ~223

Computes Schedule SE self-employment tax (15.3% = 12.4% Social Security up to the wage base + 2.9% Medicare on 92.35% of net profit), the Additional Medicare surtax, federal income tax, and an optional state income tax, plus a quarterly estimated-payment figure. Example input: { "netProfit": 90000, "filingStatus": "single", "state": "TX" }. 2026 tax year — estimates, not tax advice; brackets from Tax Foundation (Jan 1, 2026) & IRS.

NameTypeReqDescription
filingStatusstringyesIRS filing status.
netProfitnumberyesSchedule C net profit in USD (1099 income minus business expenses), e.g. 90000.
otherIncomenumber–Other ordinary income (e.g. a W-2 job) that stacks on top for bracket and wage-base purposes.
statestring–Optional two-letter US state or DC postal code to also estimate state income tax.

No output schema declared.

No examples provided.

us_take_home_pay ~323

Computes net take-home pay for a US W-2 employee: federal income tax, state income tax (all 50 states + DC), FICA (Social Security + Medicare + Additional Medicare), and state-specific extras (e.g. CA SDI, OR transit tax). Supports pre-tax 401(k) and health-insurance deductions and per-paycheck breakdowns. Example input: { "gross": 75000, "state": "CA", "filingStatus": "single" }. 2026 tax year — estimates, not tax advice; brackets from Tax Foundation (Jan 1, 2026) & IRS.

NameTypeReqDescription
dependentsinteger–Number of dependents claimed (informational; not currently used in the federal/state bracket math).
filingStatusstringyesIRS filing status.
grossnumberyesAnnual gross income in USD, e.g. 75000.
payFrequencystring–Pay frequency; the result always includes a full per-paycheck breakdown for all frequencies regardless of this value.
pretax401kPctnumber–Pre-tax 401(k) contribution as a percent of gross pay (0-100), capped at the 2026 employee deferral limit ($23,500).
pretaxHealthAnnualnumber–Annual pre-tax health insurance / HSA premiums in USD, excluded from both income tax and FICA wages.
statestringyesTwo-letter US state or DC postal code, e.g. "CA", "TX", "NY".

No output schema declared.

No examples provided.

Install

How do I install the StateTakeHome MCP server?

StateTakeHome runs locally as an npm package, launched with npx -y statetakehome-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · statetakehome-mcp

# add to Claude Code
claude mcp add tresor4k-statetakehome-mcp -- npx -y statetakehome-mcp
Common questions

What is the StateTakeHome MCP server?

StateTakeHome is an MCP server listed in the public MCP registry as io.github.tresor4k/statetakehome-mcp. US take-home pay calculator by state: federal and state tax, FICA, deductions. This page covers its npm package (statetakehome-mcp).

Is the StateTakeHome MCP server safe to use?

StateTakeHome scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 StateTakeHome MCP server expose?

StateTakeHome exposes 3 tools: us_take_home_pay, self_employment_tax, capital_gains_tax. Their descriptions and schemas cost roughly 835 tokens of context every time the server is loaded.

Is the StateTakeHome MCP server still maintained?

StateTakeHome 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 licence is the StateTakeHome MCP server under?

StateTakeHome declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the StateTakeHome MCP server?

VerifyMCP ran 16 checks on StateTakeHome, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.